{"id":538875,"date":"2026-02-18T14:02:36","date_gmt":"2026-02-18T13:02:36","guid":{"rendered":"https:\/\/silicon-saxony.de\/btu-avoiding-software-conflicts-during-development\/"},"modified":"2026-02-18T14:02:36","modified_gmt":"2026-02-18T13:02:36","slug":"btu-avoiding-software-conflicts-during-development","status":"publish","type":"post","link":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/","title":{"rendered":"BTU: Avoiding software conflicts during development"},"content":{"rendered":"<p><img decoding=\"async\" style=\"width: 25%;\" src=\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\"><\/p>\n<p>At Brandenburg University of Technology Cottbus-Senftenberg (BTU), researcher Prof. Leen Lambers is developing a proactive approach to dealing with conflicts based on graph transformations in the new DFG project &#8220;Conflict Prevention and Proactive Conflict Resolution Strategies for Graph Transformation&#8221;, or CORE-GT for short. The Head of the Department of Practical Computer Science\/Software Systems Engineering is guided by the Capability Maturity Model Integration (CMMI), a process and maturity model that supports organizations in optimizing processes and establishing efficient working methods in order to reduce risks in software, product and service development.<\/p>\n<p>&#8220;The aim of mature processes is to prevent problems as far as possible instead of reacting to them after the fact,&#8221; summarizes Prof. Lambers. &#8220;So far, however, there has been little research into how conflicts in software development can be proactively prevented or resolved.&#8221;<\/p>\n<h3 class=\"\">Graph transformation as a methodological basis<\/h3>\n<p>Graphs are a tried and tested means of representation in computer science for illustrating complex relationships or analyzing multi-layered structured data. They can be used to illustrate relationships between individual elements clearly and precisely. The concepts of graph transformation provide a powerful basis for developing an effective approach.<\/p>\n<p>According to Prof. Lambers, there are three reasons for this:<\/p>\n<ul>\n<li>Graphs are well suited to representing complex structures, such as code artifacts, system architectures or computing states.<\/li>\n<li>Changes to these structures can be clearly described using graph transformation rules.<\/li>\n<li>Graph transformation is based on a rich and well-established theory.<\/li>\n<\/ul>\n<h3 class=\"\">From prevention to solution<\/h3>\n<p>Potential conflicts should be avoided during development with the help of prepared repair proposals. If they cannot be prevented, pre-defined solution templates are used, which are applied semi-automatically if necessary and aligned to a mutually acceptable solution using heuristic search methods.<\/p>\n<p>The CORE-GT project is led by Prof. Gabriele Taentzer&nbsp; (Philipps University Marburg) and Prof. Leen Lambers. Two positions are earmarked for realizing the project ideas within three years and for completing a doctorate.<\/p>\n<h3 class=\"\">Contact<\/h3>\n<p>Prof. Dr. rer. nat. Leen Lambers<br \/>Practical Computer Science\/Software Systems Engineering&nbsp;<br \/>T +49 (0) 355 69-3880&nbsp;<br \/>lambers(at)b-tu.de<\/p>\n<p>&#8211; &#8211; &#8211; &#8211; &#8211; &#8211;<\/p>\n<h4 class=\"\">Further links<\/h4>\n<p>\ud83d\udc49&nbsp;<a href=\"http:\/\/www.b-tu.de\" target=\"_blank\">www.b-tu.de<\/a>&nbsp;&nbsp;<\/p>\n<p><i>Photo: pixabay<\/i><\/p>\n","protected":false},"excerpt":{"rendered":"<p>February 17, 2026. Conflicts are part of everyday life in software development, for example when teams work together on a system. A new DFG project at BTU Cottbus-Senftenberg and Philipps-Universit\u00e4t Marburg is now researching a proactive approach that not only recognizes conflicts, but also specifically prevents them.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[4764],"tags":[2021,11369,2016],"class_list":["post-538875","post","type-post","status-publish","format-standard","hentry","category-software-en","tag-digitization","tag-programming-software","tag-software-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.1.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>BTU: Avoiding software conflicts during development - Silicon Saxony<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BTU: Avoiding software conflicts during development - Silicon Saxony\" \/>\n<meta property=\"og:description\" content=\"February 17, 2026. Conflicts are part of everyday life in software development, for example when teams work together on a system. A new DFG project at BTU Cottbus-Senftenberg and Philipps-Universit\u00e4t Marburg is now researching a proactive approach that not only recognizes conflicts, but also specifically prevents them.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\" \/>\n<meta property=\"og:site_name\" content=\"Silicon Saxony\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-18T13:02:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\" \/>\n<meta name=\"author\" content=\"publizer2silisax\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"publizer2silisax\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\"},\"author\":{\"name\":\"publizer2silisax\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6\"},\"headline\":\"BTU: Avoiding software conflicts during development\",\"datePublished\":\"2026-02-18T13:02:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\"},\"wordCount\":359,\"image\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\",\"keywords\":[\"Digitization\",\"Programming software\",\"Software Development\"],\"articleSection\":[\"Software\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\",\"url\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\",\"name\":\"BTU: Avoiding software conflicts during development - Silicon Saxony\",\"isPartOf\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\",\"datePublished\":\"2026-02-18T13:02:36+00:00\",\"author\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6\"},\"breadcrumb\":{\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage\",\"url\":\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\",\"contentUrl\":\"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/silicon-saxony.de\/en\/home\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BTU: Avoiding software conflicts during development\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/#website\",\"url\":\"https:\/\/silicon-saxony.de\/en\/\",\"name\":\"Silicon Saxony\",\"description\":\"Germany&#039;s Hightech Network - Semiconductors, Software, Robotics\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/silicon-saxony.de\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6\",\"name\":\"publizer2silisax\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c4acbd63e28aa0bc7909adc90d5ef38c3fdb5e4c7922782d8eca389d00ffbd0d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c4acbd63e28aa0bc7909adc90d5ef38c3fdb5e4c7922782d8eca389d00ffbd0d?s=96&d=mm&r=g\",\"caption\":\"publizer2silisax\"},\"url\":\"https:\/\/silicon-saxony.de\/en\/author\/publizer2silisax\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BTU: Avoiding software conflicts during development - Silicon Saxony","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/","og_locale":"en_US","og_type":"article","og_title":"BTU: Avoiding software conflicts during development - Silicon Saxony","og_description":"February 17, 2026. Conflicts are part of everyday life in software development, for example when teams work together on a system. A new DFG project at BTU Cottbus-Senftenberg and Philipps-Universit\u00e4t Marburg is now researching a proactive approach that not only recognizes conflicts, but also specifically prevents them.","og_url":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/","og_site_name":"Silicon Saxony","article_published_time":"2026-02-18T13:02:36+00:00","og_image":[{"url":"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg","type":"","width":"","height":""}],"author":"publizer2silisax","twitter_card":"summary_large_image","twitter_misc":{"Written by":"publizer2silisax","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#article","isPartOf":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/"},"author":{"name":"publizer2silisax","@id":"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6"},"headline":"BTU: Avoiding software conflicts during development","datePublished":"2026-02-18T13:02:36+00:00","mainEntityOfPage":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/"},"wordCount":359,"image":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage"},"thumbnailUrl":"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg","keywords":["Digitization","Programming software","Software Development"],"articleSection":["Software"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/","url":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/","name":"BTU: Avoiding software conflicts during development - Silicon Saxony","isPartOf":{"@id":"https:\/\/silicon-saxony.de\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage"},"image":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage"},"thumbnailUrl":"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg","datePublished":"2026-02-18T13:02:36+00:00","author":{"@id":"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6"},"breadcrumb":{"@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#primaryimage","url":"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg","contentUrl":"https:\/\/cdn.pblzr.de\/dacbb27c-1270-4041-b681-e2b95f06f8a1\/2026\/02\/btu-logo-400x300_1_TEXT.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/silicon-saxony.de\/en\/btu-avoiding-software-conflicts-during-development\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/silicon-saxony.de\/en\/home\/"},{"@type":"ListItem","position":2,"name":"BTU: Avoiding software conflicts during development"}]},{"@type":"WebSite","@id":"https:\/\/silicon-saxony.de\/en\/#website","url":"https:\/\/silicon-saxony.de\/en\/","name":"Silicon Saxony","description":"Germany&#039;s Hightech Network - Semiconductors, Software, Robotics","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/silicon-saxony.de\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/098cd473f5dd7707320dd1e252e15ac6","name":"publizer2silisax","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/silicon-saxony.de\/en\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/c4acbd63e28aa0bc7909adc90d5ef38c3fdb5e4c7922782d8eca389d00ffbd0d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c4acbd63e28aa0bc7909adc90d5ef38c3fdb5e4c7922782d8eca389d00ffbd0d?s=96&d=mm&r=g","caption":"publizer2silisax"},"url":"https:\/\/silicon-saxony.de\/en\/author\/publizer2silisax\/"}]}},"_links":{"self":[{"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/posts\/538875","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/comments?post=538875"}],"version-history":[{"count":0,"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/posts\/538875\/revisions"}],"wp:attachment":[{"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/media?parent=538875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/categories?post=538875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/silicon-saxony.de\/en\/wp-json\/wp\/v2\/tags?post=538875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}