default search action
Patrick Rempel
Person information
- affiliation: TU Ilmenau, Department of Computer Science, Germany
- affiliation: Oxford Computer Group GmbH, Munich, Germany
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
- [c15]Andreas Stichow, Patrick Rempel:
Securing Electric Vehicle Charging Stations: A Critical Analysis of Authentication Vulnerabilities. RE Workshops 2024: 231-240 - 2022
- [i1]Johan Linåker, Patrick Rempel, Björn Regnell, Patrick Mäder:
How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns. CoRR abs/2208.02628 (2022)
2010 – 2019
- 2017
- [j2]Patrick Rempel, Patrick Mäder:
Preventing Defects: The Impact of Requirements Traceability Completeness on Software Quality. IEEE Trans. Software Eng. 43(8): 777-797 (2017) - [c14]Michael Rath, Patrick Rempel, Patrick Mäder:
The IlmSeven Dataset. RE 2017: 516-519 - [c13]Hongyu Kuang, Jia Nie, Hao Hu, Patrick Rempel, Jian Lu, Alexander Egyed, Patrick Mäder:
Analyzing closeness of code dependencies for improving IR-based Traceability Recovery. SANER 2017: 68-78 - 2016
- [b1]Patrick Rempel:
Continuous assessment of software traceability. Technische Universität Ilmenau, Germany, 2016 - [c12]Patrick Rempel, Patrick Mäder:
Continuous assessment of software traceability. ICSE (Companion Volume) 2016: 747-748 - [c11]Johan Linåker, Patrick Rempel, Björn Regnell, Patrick Mäder:
How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns. REFSQ 2016: 63-81 - [c10]Patrick Rempel, Patrick Mäder:
A quality model for the systematic assessment of requirements traceability. Software Engineering 2016: 37-38 - 2015
- [c9]Patrick Rempel, Patrick Mäder:
A quality model for the systematic assessment of requirements traceability. RE 2015: 176-185 - [c8]Patrick Rempel, Patrick Mäder:
Estimating the Implementation Risk of Requirements in Agile Software Development Projects with Traceability Metrics. REFSQ 2015: 81-97 - [c7]Patrick Rempel, Patrick Mäder, Tobias Kuschke, Jane Cleland-Huang:
Traceability Gap Analysis for Assessing the Conformance of Software Traceability to Relevant Guidelines. Software Engineering & Management 2015: 120-121 - 2014
- [c6]Patrick Rempel, Patrick Mäder, Tobias Kuschke, Jane Cleland-Huang:
Mind the gap: assessing the conformance of software traceability to relevant guidelines. ICSE 2014: 943-954 - 2013
- [c5]Patrick Rempel, Patrick Mäder, Tobias Kuschke:
Towards feature-aware retrieval of refinement traces. TEFSE@ICSE 2013: 100-104 - [c4]Tobias Kuschke, Patrick Mäder, Patrick Rempel:
Recommending Auto-completions for Software Modeling Activities. MoDELS 2013: 170-186 - [c3]Patrick Rempel, Patrick Mäder, Tobias Kuschke:
An empirical study on project-specific traceability strategies. RE 2013: 195-204 - [c2]Patrick Rempel, Patrick Mäder, Tobias Kuschke, Ilka Philippow:
Requirements Traceability across Organizational Boundaries - A Survey and Taxonomy. REFSQ 2013: 125-140 - 2012
- [j1]Patrick Rempel, Steffen Lehnert, Tobias Kuschke, Qurat-ul-ann Farooq:
A Framework for Traceability Tool Comparison. Softwaretechnik-Trends 32(3) (2012) - 2010
- [c1]Patrick Rempel, Basel Katt, Ruth Breu:
Supporting Role Based Provisioning with Rules Using OWL and F-Logic. OTM Conferences (1) 2010: 600-618
Coauthor Index
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-09-05 23:44 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint