Hendrik Bünder

Hendrik is an IT consultant at itemis AG in Bonn. He works on projects utilizing Xtext to build integrated toolchains. He is interested in model driven software development, DSLs and software architecture.
Hendrik Bünder

Recent Posts

Building Domain-specific Languages with Xtext and Xtend

Specifying the requirements of a software system and converting such a specification into executable source code is difficult and error-prone. Requirements specifications written in prose are often ambiguous and hard to understand for developers. Therefore, the process of turning this documents into software is slow and prone to error. Domain-specific languages (DSL) challenge this problem by defining a semantically rich notation to describe domain concepts clear and concise. Read more >

A UML-agnostic Migration Approach: From UML to DSL

Over the last decade, open source frameworks for creating domain-specific language workbenches have improved significantly. Thereby, it has become easier to utilize model-driven software engineering based on domain-specific languages (DSL). However, many companies already adopted model-driven engineering at the beginning of the 21st century.  Read more >

Domain-specific visualization of textual models with Xtext and Sirius

Some people say graphical modeling is dead and textual modeling is the better maybe the only way. As an Xtext-enthusiast I would always argue that modeling should be done textually.  Read more >

What I learned introducing a domain-specific language for configurable traceability analysis

At this years Modelsward conference I had the opportunity to present a paper about "A Domain-specific Language for Configurable Traceability Analysis" that was written in close collaboration with Prof. Dr. Kuchen and Christoph Rieger from [ERCIS] of the University of Muenster. Read more >

Xtext hint: Content assist for multiple consecutive keywords

Keywords play a central role in Xtext DSLs to define the languages general structure. In many cases a single keyword is sufficient to specify what is expected next. Although Xtext generally supports multiple consecutive keywords the default content assist implementation will propose one keyword after another instead of concatenating consecutive keywords. This can lead to confusing proposals for the user. This article will help you to prevent this confusion. Read more >


Popular posts