Logo des Repositoriums

Auflistung nach Autor:in "Knodel, Jens"

1 - 10 von 15
  • Konferenz-Abstract
    23. Workshop Software-Reengineering und -Evolution (WSRE) – 12. Workshop „Design for Future“ des GI-Arbeitskreises Langlebige Softwaresysteme (L2S2)
    (Softwaretechnik-Trends Band 41, Heft 1, 2021) Knodel, Jens; Konersmann, Marco; Görg, Torsten; Gutheil, Matthias; Sauer, Stefan; Heinrich, Robert; Konersmann, Marco; Sauer, Stefan
    Ziel des Treffens war es, einander kennen zu lernen und auf diesem Wege eine direkte Basis für Kooperationen zu schaffen, so dass das Themengebiet eine Stärkung, Konsolidierung und Weiterentwicklung erfährt. Das diesjährige Workshop-Programm enthielt die folgenden Programmpunkte: (1) Keynote-Vortrag von Elmar Jürgens: "Ist das wichtig oder kann das weg? Überraschende Ergebnisse dynamischer Analysen im Großen"; (2) Fachvortrag von David Morais Ferreira, Vasil L. Tenev und Martin Becker: "Deriving Goals From Well Known Industrial Cases of Product Line Engineering Adoption"; (3) Interaktive Session aller Teilnehmerinnen und Teilnehmer unter Moderation von Marco Konersmann zu Ideen, Vorschlägen, Aktivitäten und dem inhaltlichen Austausch über die Erstellung einer "Wissensbasis im Software Reengineering“ als gemeinsame Aktivität in Koordination durch die Fachgruppe SRE.
  • Konferenz-Abstract
    Call for Papers: 22. Workshop Software-Reengineering & -Evolution WSRE 2020 der GI-Fachgruppe Software-Reengineering (SRE)
    (Softwaretechnik-Trends Band 39, Heft 4, 2019) Knodel, Jens; Görg, Torsten; Gutheil, Matthias; Konersmann, Marco; Sauer, Stefan
    Unser Ziel ist die Förderung der Zusammenarbeit und der fachliche Austausch zwischen Forschung und Praxis im deutschsprachigen Raum zu den Themen „Software-Reengineering“, „Software-Wartung“ und „Software-Evolution“. Darunter verstehen wir prinzipiell alle Aktivitäten, deren Ziel die Analyse, Visualisierung, Bewertung, Verbesserung, Migration und Weiterentwicklung von größeren und kleineren Software-Systemen ist. Wir laden Forscher und Praktiker herzlich ein, beim WSRE über Erfahrungen, Projekte, Forschungsergebnisse, Methoden, Werkzeuge, und „War-Stories“ in diesem Bereich zu berichten, ihre aktuellen Arbeiten vorzustellen und in einem offenen Umfeld konstruktiv zu diskutieren.
  • Zeitschriftenartikel
    Case Studies of Static Software Architecture Evaluations
    (Softwaretechnik-Trends Band 26, Heft 2, 2006) Knodel, Jens; Lindvall, Mikael; Muthig, Naab
    Architecture evaluations play an important role in the development and evolution of software systems since they determine how adequate the architecture is for its intended usage. This paper summarizes our practical experience with using static architecture evaluations and gives an overview on when and how static architecture evaluations contribute to architecture development. In particular, we identify ten distinct purposes and needs for static architecture evaluations derived from practical experiences in a set of industrial and academic case studies.
  • Konferenzbeitrag
    A Decade of Reverse Engineering at Fraunhofer IESE – The Changing Role of Reverse Engineering in Applied Research
    (Software archeology and the handbook of software architecture, 2008) Knodel, Jens; Muthig, Dirk
    The Fraunhofer Institute for Experimental Software Engineering (IESE) recognized reverse engineering as an essential competence and thus has been active in the field since 1996, which is right from its beginning. The role of reverse engineering, however, within the institute changed over time. Since Fraunhofer IESE is an applied research institute its competencies are tailored to the market to be and stay attractive to industry. This paper analyzes the evolution of the competence reverse engineering in retrospective and derives a picture of the role and importance of reverse engineering to practice in the last ten years where reverse engineering moved from a set of techniques applied in pure reengineering project to an enabling technology for other software engineering disciplines. Furthermore, we present our vision for the future role of reverse engineering at Fraunhofer IESE, as a supportive technology for the development of software, which gives constant and continuous feedback already at construction time.
  • Konferenzbeitrag
    FG SRE / AK DFF: Bericht und Beiträge vom 21. Workshop Software-Reengineering und -Evolution (WSRE) und 10. Workshop Design for Future (DFF), am 06. und 08. Mai 2019 in Bad Honnef
    (Softwaretechnik-Trends Band 39, Heft 2, 2019) Knodel, Jens; Görg, Torsten; Borchers, Jens; Gutheil, Matthias; Sauer, Stefan; Heinrich, Robert; Konersmann, Marco; Sauer, Stefan
    Die Workshops Software-Reengineering (WSR) im Physikzentrum Bad Honnef wurden mit dem ersten WSR 1999 von Jürgen Ebert und Franz Lehner ins Leben gerufen, um neben den internationalen erfolgreichen Tagungen auch ein deutschsprachiges Diskussionsforum zum Thema Reengineering zu schaffen. Seit 2014 firmiert der Workshop unter dem Titel „Software-Reengineering & -Evolution“ (WSRE), um der Weiterentwicklung des Themengebiets Rechnung zu tragen und eine breitere Zielgruppe anzusprechen.
  • Zeitschriftenartikel
    From Architecture to Source Code – How to Ensure Architecture Compliance in the Implemented System
    (Softwaretechnik-Trends Band 29, Heft 2, 2009) Knodel, Jens
    Software architecture is the key factor for efficient communication, planning, development, maintenance, and hence, the overall success of the development project. Architecting is an upfront investment made by development organizations to assure that the resulting system(s) will meet the required quality criteria in time and effort. Among others, the software architecture captures the envisioned structure of the system at development time (i.e., the decomposition of the system in manageable units like components). Verifying this planned decomposition late in the lifecycle of the software system reveals – too often – that the implemented system is not compliant to the specified structure. Consequently, efforts spent for architecting were made in vain because the decision and assumption made are no longer reliable and useful. To pro-actively prevent this structural decay, we propose constructive architecture compliance checking, which constantly monitors the modifications made by several (teams of) developers starting at day one of the implementation phase. Whenever structural violations are detected, the particular developer receives live feedback on the violations. Thus, a prompt removal of violations is possible, which ensures compliance of the implemented system with the architecture. Hence, the investments made into architecting are sustained over time.
  • Zeitschriftenartikel
    Maintainability is a Versatile Quality Attribute
    (Softwaretechnik-Trends Band 36, Heft 3, 2016) Knodel, Jens; Naab, Matthias
    Software architecture evaluation has been widely accepted as a powerful means to mitigate risks in the design and evolution of software systems. To date we have conducted more than 75 architecture evaluation projects with industrial customers in the past decade. One recurring lesson learned that we experienced across many architecture evaluation projects is that maintainability indeed is a versatile quality attribute and its evaluation requires a mix of quantitative and qualitative checks.
  • Zeitschriftenartikel
    Mitigating the Risk of Software Change in Practice Retrospective on More Than 50 Architecture Evaluations in Industry (Keynote Paper)
    (Softwaretechnik-Trends Band 34, Heft 2, 2014) Knodel, Jens; Naab, Matthias
    Architecture evaluation has become a mature instrument to make decisions about software systems, assess and mitigate risks, and to identify ways for improvement and migration of software systems. While scientific literature on approaches is available, publications on practical experiences are rather limited. In this paper, we share our experiences - after having performed more than 50 architecture evaluations for industrial customers in the last decade. We compiled facts and consolidate our findings about architecture evaluations in industry and especially highlight the role of reverse engineering in these projects. We share our lessons learned and provide data on common believes and provide examples for common misconceptions on the power of reverse engineering. This industrial and practical perspective allows practitioners to benefit from our experience in their daily architecture work and how to guide research of the scientific community.
  • Zeitschriftenartikel
    Modularity – Often Desired, but Rarely Achieved
    (Softwaretechnik-Trends Band 35, Heft 2, 2015) Knodel, Jens; Naab, Matthias; Weitzel, Balthasar
    “Everything should be modular” is an exalted goal stated by almost every architect – but is it really possible to achieve this goal? In this experience paper, we share our lessons learned across a number of restructuring projects that went modular. We discuss typical business motivations, restructuring efforts starting with good intentions, and reconstruction reality striking back. In retrospective, we analyze typical pitfalls to be circumvented. Examples illustrate our findings and support a truism too often ignored by architects: everything has its price, and more often than not, the price for modularity is a lot higher than initially estimated.
  • Textdokument
    The Need for an Open Corpus of Software Architecture Descriptions
    (Softwaretechnik-Trends: Vol. 37, No. 2, 2017) Knodel, Jens; Buckley, Jim; Herold, Sebastian
    Software architectures are the conceptual tool to share information about key aspects of a software system and to enable reasoning about the principal, most fundamental, and often most difficult-to-change design decisions of the system. Studies of failed software systems give evidence that architecture drift, erosion or degradation is a prevalent problem in industrial practice. But a recent systematic literature review [9] indicates that research currently investigates compliance checking or inconsistency detection only. To advance research we need an open and grounded corpus of software architecture description – serving as a basis for more sophisticated studies beyond detection only. Such a corpus could enable (1) to evaluate new approaches, (2) to provide means for fixing degradation (when it occurs or a-posteriori), (3) to compare and benchmark approaches and, ultimately, (4) enable longitudinal studies in the field.