default search action
Henning Femmer
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
- [c38]Marcel Koschinsky, Henning Femmer, Claudia Schindler:
A Process Proposal for Requirements Engineering for Third-Party Products and a Preliminary Evaluation at Munich Re. SWQD 2024: 3-17 - 2023
- [i8]Henning Femmer, Michael Unterkalmsteiner, Tony Gorschek:
Which Requirements Artifact Quality Defects are Automatically Detectable? A Case Study. CoRR abs/2308.15057 (2023) - 2022
- [c37]Maximilian Junker, Henning Femmer:
Modeling an Anomaly Detection System with SpesML. Modellierung (Workshops) 2022: 106-120 - 2021
- [j5]Henning Femmer:
Die Ära der Assistenzfunktionen im Requirements Engineering. Softwaretechnik-Trends 42(1): 18-19 (2021) - [c36]Jannik Fischbach, Julian Frattini, Daniel Méndez, Michael Unterkalmsteiner, Henning Femmer, Andreas Vogelsang:
How Do Practitioners Interpret Conditionals in Requirements? PROFES 2021: 85-102 - [c35]Jannik Fischbach, Tobias Springer, Julian Frattini, Henning Femmer, Andreas Vogelsang, Daniel Méndez:
Fine-Grained Causality Extraction From Natural Language Requirements Using Recursive Neural Tensor Networks. RE Workshops 2021: 60-69 - [c34]Henning Femmer:
Assisted Requirements Engineering - What Will Remain in the Hands of the Future Requirements Engineer? (Invited Keynote). SWQD 2021: 3-14 - [i7]Jannik Fischbach, Tobias Springer, Julian Frattini, Henning Femmer, Andreas Vogelsang, Daniel Méndez:
Fine-Grained Causality Extraction From Natural Language Requirements Using Recursive Neural Tensor Networks. CoRR abs/2107.09980 (2021) - [i6]Jannik Fischbach, Julian Frattini, Daniel Méndez, Michael Unterkalmsteiner, Henning Femmer, Andreas Vogelsang:
How Do Practitioners Interpret Conditionals in Requirements? CoRR abs/2109.02063 (2021) - 2020
- [c33]Jannik Fischbach, Henning Femmer, Daniel Méndez, Davide Fucci, Andreas Vogelsang:
What Makes Agile Test Artifacts Useful?: An Activity-Based Quality Model from a Practitioners' Perspective. ESEM 2020: 41:1-41:10 - [c32]Katharina Winter, Henning Femmer, Andreas Vogelsang:
How Do Quantifiers Affect the Quality of Requirements? REFSQ 2020: 3-18 - [c31]Henning Femmer, Axel Müller, Sebastian Eder:
Semantic Similarities in Natural Language Requirements. SWQD 2020: 87-105 - [i5]Katharina Winter, Henning Femmer, Andreas Vogelsang:
How do Quantifiers Affect the Quality of Requirements? CoRR abs/2002.02672 (2020) - [i4]Jannik Fischbach, Henning Femmer, Daniel Méndez, Davide Fucci, Andreas Vogelsang:
What Makes Agile Test Artifacts Useful? An Activity-Based Quality Model from a Practitioners' Perspective. CoRR abs/2009.01722 (2020)
2010 – 2019
- 2019
- [j4]Henning Femmer, Andreas Vogelsang:
Requirements Quality Is Quality in Use. IEEE Softw. 36(3): 83-91 (2019) - 2018
- [j3]Andreas Vogelsang, Jonas Paul Winkler, Henning Femmer:
Towards Explainable RE Tools. Softwaretechnik-Trends 38(1): 43-44 (2018) - [c30]Luca Allodi, Sebastian Banescu, Henning Femmer, Kristian Beckers:
Identifying Relevant Information Cues for Vulnerability Assessment Using CVSS. CODASPY 2018: 119-126 - [c29]Henning Femmer:
Requirements Quality Defect Detection with the Qualicen Requirements Scout. REFSQ Workshops 2018 - [i3]Luca Allodi, Sebastian Banescu, Henning Femmer, Kristian Beckers:
Identifying Relevant Information Cues for Vulnerability Assessment Using CVSS. CoRR abs/1803.07648 (2018) - 2017
- [b1]Henning Femmer:
Requirements Engineering Artifact Quality: Definition and Control (Qualität von Anforderungsartefakten: Definition und Steuerung). Technical University of Munich, Germany, 2017 - [j2]Henning Femmer, Daniel Méndez Fernández, Stefan Wagner, Sebastian Eder:
Rapid quality assurance with Requirements Smells. J. Syst. Softw. 123: 190-213 (2017) - [j1]Henning Femmer, Andreas Vogelsang:
Good RE Artifacts? I Know It When I Use It! Softwaretechnik-Trends 37(2) (2017) - [c28]Henning Femmer:
Automatic Requirements Reviews - Potentials, Limitations and Practical Tool Support. PROFES 2017: 617-620 - [c27]Alistair Mavin, Philip Wilkinson, Sabine Teufl, Henning Femmer, Jonas Eckhardt, Jakob Mund:
Does Goal-Oriented Requirements Engineering Achieve Its Goal? RE 2017: 174-183 - [c26]Armin Beer, Maximilian Junker, Henning Femmer, Michael Felderer:
Initial Investigations on the Influence of Requirement Smells on Test-Case Design. RE Workshops 2017: 323-326 - [c25]Henning Femmer, Michael Unterkalmsteiner, Tony Gorschek:
Which Requirements Artifact Quality Defects are Automatically Detectable? A Case Study. RE Workshops 2017: 400-406 - [c24]Andreas Vogelsang, Henning Femmer, Maximilian Junker:
Characterizing Implicit Communal Components as Technical Debt in Automotive Software Systems. Software Engineering 2017: 71-72 - [i2]Jakob Mund, Henning Femmer, Daniel Méndez Fernández, Jonas Eckhardt:
Does Quality of Requirements Specifications matter? Combined Results of Two Empirical Studies. CoRR abs/1702.07656 (2017) - 2016
- [c23]Henning Femmer, Benedikt Hauptmann, Sebastian Eder, Dagmar Moser:
Quality Assurance of Requirements Artifacts in Practice: A Case Study and a Process Proposal. PROFES 2016: 506-516 - [c22]Fabiano Dalpiaz, Henning Femmer, Jin Guo:
Welcome to the Third International Workshop on Artificial Intelligence for Requirements Engineering (AIRE'16). RE Workshops 2016: 1 - [c21]Jonas Eckhardt, Andreas Vogelsang, Henning Femmer, Philipp Mager:
Challenging Incompleteness of Performance Requirements by Sentence Patterns. RE 2016: 46-55 - [c20]Jonas Eckhardt, Andreas Vogelsang, Henning Femmer:
An Approach for Creating Sentence Patterns for Quality Requirements. RE Workshops 2016: 308-315 - [c19]Andreas Vogelsang, Henning Femmer, Christian Winkler:
Take Care of Your Modes! An Investigation of Defects in Automotive Requirements. REFSQ 2016: 161-167 - [c18]Andreas Vogelsang, Henning Femmer, Maximilian Junker:
Characterizing Implicit Communal Components as Technical Debt in Automotive Software Systems. WICSA 2016: 31-40 - [i1]Henning Femmer, Daniel Méndez Fernández, Stefan Wagner, Sebastian Eder:
Rapid quality assurance with Requirements Smells. CoRR abs/1611.08847 (2016) - 2015
- [c17]Jakob Mund, Daniel Méndez Fernández, Henning Femmer, Jonas Eckhardt:
Does Quality of Requirements Specifications Matter? Combined Results of Two Empirical Studies. ESEM 2015: 144-153 - [c16]Henning Femmer, Jakob Mund, Daniel Méndez Fernández:
It's the Activities, Stupid! A New Perspective on RE Quality. RET@ICSE 2015: 13-19 - [c15]Sebastian Eder, Henning Femmer, Benedikt Hauptmann, Maximilian Junker:
Configuring Latent Semantic Indexing for Requirements Tracing. RET@ICSE 2015: 27-33 - [c14]Maximilian Junker, Manfred Broy, Benedikt Hauptmann, Wolfgang Böhm, Henning Femmer, Sebastian Eder, Elmar Jürgens, Rainer Janßen, Rudolf Vaas:
Principles and a Process for Successful Industry Cooperation - The Case of TUM and Munich Re. SER&IP@ICSE 2015: 50-53 - [c13]Andreas Vogelsang, Henning Femmer, Christian Winkler:
Systematic elicitation of mode models for multifunctional systems. RE 2015: 305-314 - [c12]Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, Alexander Widera:
Understanding changes in use cases: A case study. RE 2015: 352-361 - 2014
- [c11]Daniel Méndez Fernández, Jakob Mund, Henning Femmer, Antonio Vetrò:
In quest for requirements engineering oracles: dependent variables and measurements for (good) RE. EASE 2014: 3:1-3:10 - [c10]Birgit Penzenstadler, Ankita Raturi, Debra J. Richardson, Coral Calero, Henning Femmer, Xavier Franch:
Systematic mapping study on software engineering for sustainability (SE4S). EASE 2014: 14:1-14:14 - [c9]Henning Femmer, Jan Kucera, Antonio Vetrò:
On the impact of passive voice requirements on domain modelling. ESEM 2014: 21:1-21:4 - [c8]Henning Femmer, Marco Kuhrmann, Jörg Stimmer, Jorg Junge:
Experiences from the Design of an Artifact Model for Distributed Agile Project Management. ICGSE 2014: 1-5 - [c7]Henning Femmer, Daniel Méndez Fernández, Elmar Jürgens, Michael Klose, Ilona Zimmer, Jörg Zimmer:
Rapid requirements checks with requirements smells: two case studies. RCoSE 2014: 10-19 - [c6]Sebastian Eder, Henning Femmer, Benedikt Hauptmann, Maximilian Junker:
Which Features Do My Users (Not) Use? ICSME 2014: 446-450 - 2013
- [c5]Birgit Penzenstadler, Henning Femmer:
A generic model for sustainability with process- and product-specific instances. GIBSE@AOSD 2013: 3-8 - [c4]Birgit Penzenstadler, Henning Femmer, Debra J. Richardson:
Who is the advocate? Stakeholders for sustainability. GREENS 2013: 70-77 - [c3]Henning Femmer, Dharmalingam Ganesan, Mikael Lindvall, David McComas:
Detecting inconsistencies in wrappers: a case study. ICSE 2013: 1022-1031 - [c2]Birgit Penzenstadler, Henning Femmer:
RE@21: Time to Sustain! RE4SuSy@RE 2013 - 2011
- [c1]Henning Femmer, Nora Broy, Marin Zec, Asa MacWilliams, Roland Eckl:
Dynamic Software Visualization with BusyBorg - A Proof of Concept. COMPSAC 2011: 492-497
Coauthor Index
aka: Daniel Méndez Fernández
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-10-07 21:21 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint