Auflistung nach Autor:in "Prechelt, Lutz"
1 - 8 von 8
Treffer pro Seite
Sortieroptionen
- ZeitschriftenartikelArbeitsgruppenvorstellung: AG Software Engineering, FU Berlin (Prof. Dr. Lutz Prechelt): Die Empirie-Dienstleister(Softwaretechnik-Trends Band 28, Heft 3, 2008) Prechelt, Lutz
- KonferenzbeitragBenutzeranforderungen als Zentrum und Treiber im Portalbauprozess(INFORMATIK 2003 – Innovative Informatikanwendungen, Band 2, Beiträge der 33. Jahrestagung der Gesellschaft für Informatik e.V. (GI), 2003) Prechelt, LutzDie Umsetzung eines Portals ist eine technisch schwierige und komplexe Aufgabe. Dennoch resultieren die schlimmsten Mängel des Endprodukts meist nicht aus technischen Fehlern, sondern von falsch oder unvollständig ermittelten oder umgesetzten Anforderungen. Dieser Beitrag beschreibt technische Maßnahmen, mit deren Hilfe die Anforderungsbestimmung beim Portalbau so mit der technischen Umsetzung verzahnt werden kann, dass solche Mängel weniger wahrscheinlich werden.
- ZeitschriftenartikelErnst Denert Software-Engineering-Preis 2021(Softwaretechnik-Trends Band 42, Heft 2, 2022) Felderer, Michael; Hasselbring, Wilhelm; Koziolek, Heiko; Lilienthal, Carola; Matthes, Florian; Prechelt, Lutz; Reussner, Ralf; Rumpe, Bernhard; Schaefer, InaVorwort zum Ernst Denert Software-Engineering-Preis 2021
- ConferencePaperExplaining Pair Programming Session Dynamics from Knowledge Gaps(Software Engineering 2021, 2021) Zieris, Franz; Prechelt, LutzBackground: Despite a lot of research on the effectiveness of Pair Programming (PP), the question when it is useful or less useful remains unsettled. Method: We analyze recordings of many industrial PP sessions with Grounded Theory Methodology and build on prior work that identified various phenomena related to within-session knowledge build-up and transfer. We validate our findings with practitioners. Result: We identify two fundamentally different types of required knowledge and explain how different constellations of knowledge gaps in these two respects lead to different session dynamics. Gaps in project-specific systems knowledge are more hampering than gaps in general programming knowledge and are dealt with first and foremost in a PP session. Conclusion: Partner constellations with complementary knowledge make PP a particularly effective practice. In PP sessions, differences in system understanding are more important than differences in general software development knowledge.
- KonferenzbeitragObservations on Knowledge Transfer of Professional Software Developers during Pair Programming(Software Engineering und Software Management 2018, 2018) Zieris, Franz; Prechelt, LutzThis work was presented at the 38th International Conference on Software Engineering (2016). Context: Software development is knowledge-intense work, and so is pair programming. However, the importance of knowledge transfer in pair programming is usually only stressed for expert-novice constellations and not for general software development situations. Goal: Understand how pair programmers deal with their knowledge deficits and eventually provide guidance for practitioners. Method: Detailed qualitative data analysis of full-length recordings of industrial pair programming sessions. Results: Expert software developers need to transfer knowledge, too, in order to conduct productive pair programming sessions. There is a diversity of beneficial and potentially problematic patterns, which even good pairs do not steadily apply or avoid, respectively. Conclusions: Pair programming is a versatile practice that even experts can profit from. Knowledge transfer skills do not automatically emerge from good software development skills, but can probably be learned.
- KonferenzbeitragOn knowledge transfer skill in pair programming(Software-engineering and management 2015, 2015) Zieris, Franz; Prechelt, LutzContext: General knowledge transfer is often considered a valuable effect or side-effect of pair programming, but even more important is its role for the success of the pair programming session itself: The partners often need to explain an idea to carry the process forward. Goal: Understand the mechanisms at work when knowledge is transferred during a pair programming session; provide practical advice for constructive behavior. Method: Qualitative data analysis of recordings of actual industrial pair programming sessions. Results: Some pairs are much more efficient in their knowledge transfer than others. These pairs manage to (1) not attempt to explain multiple things at once, (2) not lose sight of a topic, (3) clarify difficult points in stages.
- KonferenzbeitragQuality Experience(Software Engineering und Software Management 2018, 2018) Prechelt, Lutz; Schmeisky, Holger; Zieris, FranzThis work was presented at the 38th International Conference on Software Engineering (2016). Context: While successful conventional software development regularly employs separate testing staff, there are successful agile teams with as well as without separate testers. Question: How does successful agile development work without separate testers? What are advantages and disadvantages? Method: A case study, based on Grounded Theory evaluation of interviews and direct observation of three agile teams; one having separate testers, two without. All teams perform long-term development of parts of e-business web portals. Results: Teams without testers use a "quality experience" work mode centered around a tight field-use feedback loop, driven by a feeling of responsibility, supported by test automation, resulting in frequent deployments. Conclusion: In the given domain, hand-overs to separate testers appear to hamper the feedback loop more than they contribute to quality, so working without testers is preferred. However, Quality Experience is achievable only with modular architectures and in suitable domains.
- ZeitschriftenartikelDas Springerproblem(Informatik Spektrum: Vol. 15, No. 3, 1992) Nievergelt, Jürg; Prechelt, Lutz; Wegener, Ingo