@inbook{32417, author = {{Tönsing, Johanna}}, booktitle = {{Interpretationsverfahruen der germanistischen Literaturdidaktik und didaktische Referenzkonzepte}}, editor = {{Bernhardt, Sebastian and Hardtke, Thomas}}, title = {{{(K)eine kinderleichte Gattung: Konsequenzen einer kulturwissenschaftlich informierten Märchendidaktik}}}, year = {{2022}}, } @phdthesis{32414, author = {{Lass, Michael}}, publisher = {{Universität Paderborn}}, title = {{{Bringing Massive Parallelism and Hardware Acceleration to Linear Scaling Density Functional Theory Through Targeted Approximations}}}, doi = {{10.17619/UNIPB/1-1281}}, year = {{2022}}, } @inbook{32418, author = {{Tönsing, Johanna}}, booktitle = {{Sammelband über den deutsch-türkischen Film}}, editor = {{Schulte-Eickholt, Swen and Hofmann, Michael}}, title = {{{Über „Gleis 11“ [Dokumentarfilm von 2021]}}}, year = {{2022}}, } @inbook{32423, author = {{Tönsing, Johanna}}, booktitle = {{Neue Perspektiven einer kulturwissenschaftlichen Literaturdidaktik}}, editor = {{Hofmann, Michael}}, title = {{{Weiblichkeitsdiskurse in der Gegenwartsliteratur und deren Thematisierung im genderorientierten Unterricht}}}, year = {{2022}}, } @inproceedings{32410, abstract = {{Static analysis tools support developers in detecting potential coding issues, such as bugs or vulnerabilities. Research on static analysis emphasizes its technical challenges but also mentions severe usability shortcomings. These shortcomings hinder the adoption of static analysis tools, and in some cases, user dissatisfaction even leads to tool abandonment. To comprehensively assess the current state of the art, this paper presents the first systematic usability evaluation in a wide range of static analysis tools. We derived a set of 36 relevant criteria from the scientific literature and gathered a collection of 46 static analysis tools complying with our inclusion and exclusion criteria - a representative set of mainly non-proprietary tools. Then, we evaluated how well these tools fulfill the aforementioned criteria. The evaluation shows that more than half of the considered tools offer poor warning messages, while about three-quarters of the tools provide hardly any fix support. Furthermore, the integration of user knowledge is strongly neglected, which could be used for improved handling of false positives and tuning the results for the corresponding developer. Finally, issues regarding workflow integration and specialized user interfaces are proved further. These findings should prove useful in guiding and focusing further research and development in the area of user experience for static code analyses.}}, author = {{Nachtigall, Marcus and Schlichtig, Michael and Bodden, Eric}}, booktitle = {{Proceedings of the 31st ACM SIGSOFT International Symposium on Software Testing and Analysis}}, isbn = {{9781450393799}}, keywords = {{Automated static analysis, Software usability}}, pages = {{532 -- 543}}, publisher = {{ACM}}, title = {{{A Large-Scale Study of Usability Criteria Addressed by Static Analysis Tools}}}, doi = {{10.1145/3533767}}, year = {{2022}}, } @inproceedings{31133, abstract = {{Application Programming Interfaces (APIs) are the primary mechanism that developers use to obtain access to third-party algorithms and services. Unfortunately, APIs can be misused, which can have catastrophic consequences, especially if the APIs provide security-critical functionalities like cryptography. Understanding what API misuses are, and for what reasons they are caused, is important to prevent them, e.g., with API misuse detectors. However, definitions and nominations for API misuses and related terms in literature vary and are diverse. This paper addresses the problem of scattered knowledge and definitions of API misuses by presenting a systematic literature review on the subject and introducing FUM, a novel Framework for API Usage constraint and Misuse classification. The literature review revealed that API misuses are violations of API usage constraints. To capture this, we provide unified definitions and use them to derive FUM. To assess the extent to which FUM aids in determining and guiding the improvement of an API misuses detectors' capabilities, we performed a case study on CogniCrypt, a state-of-the-art misuse detector for cryptographic APIs. The study showed that FUM can be used to properly assess CogniCrypt's capabilities, identify weaknesses and assist in deriving mitigations and improvements. And it appears that also more generally FUM can aid the development and improvement of misuse detection tools.}}, author = {{Schlichtig, Michael and Sassalla, Steffen and Narasimhan, Krishna and Bodden, Eric}}, booktitle = {{2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)}}, keywords = {{API misuses, API usage constraints, classification framework, API misuse detection, static analysis}}, pages = {{673 -- 684}}, title = {{{FUM - A Framework for API Usage constraint and Misuse Classification}}}, doi = {{https://doi.org/10.1109/SANER53432.2022.00085}}, year = {{2022}}, } @misc{32399, author = {{Vahle, Ella}}, title = {{{Modelling and Proving Security for a Secure MPC Protocol for Stable Matching}}}, year = {{2022}}, } @misc{6561, author = {{Hetkämper, Tim}}, title = {{{Visualisierung von Ultraschallfeldern mittels Schlierentechnik und fraktionaler Fouriertransformation}}}, year = {{2022}}, } @misc{6592, author = {{Claes, Leander}}, title = {{{Messverfahren für die akustische Absorption zur Bestimmung der Volumenviskosität}}}, year = {{2022}}, } @inproceedings{32446, author = {{Mügge, Nils and Kronberg, Alexander and Glushenkov, Maxim and Kenig, Eugeny}}, booktitle = {{Annual Meeting on Reaction Engineering and ProcessNet Subject Division Heat and Mass Transfer}}, location = {{Würzburg, Germany}}, title = {{{Heat regeneration model for external heat engines operating with dense working fluids}}}, year = {{2022}}, }