
Efficient Domain-Specific Modeling with AI Agents, MPS and Portalon
Portalon 1.5 connects AI agents to JetBrains MPS: strong performance, broad functionality and secure deployment.
Read Article
Dr. Klaus Birken
10 min readHolistic protection and seamless traceability for cybersecurity, functional safety, and the Cyber Resilience Act
OverviewMethodological excellence and tailored tools for model-based system and software engineering.
OverviewEnterprise software from a single source: AI integration, legacy migration and full-stack development — cost-efficiently and sovereignly hosted.
Overview
Dr. Klaus Birken
6 min read
When a feature is renamed, variation conditions in the development artifacts often become outdated without notice. Or a variant contains an architecture component whose referenced requirement was removed during filtering. Such errors are not isolated cases; they arise systematically from the loose coupling between variant management tools and the other development artifacts. A tighter integration resolves these problems fundamentally and, in addition, opens up analysis capabilities which are rarely used in practice today.
For the development of product families, a formal description of the entire possible product space is indispensable. For this purpose, Feature-Oriented Domain Analysis (FODA) has been an established approach for more than three decades: feature diagrams describe all decisions required to configure a concrete product, along with the applicable constraints.
A feature diagram follows a hierarchical tree structure. Each node represents a product characteristic (feature). Optional features, alternatives (XOR), and OR groups are expressed using standardised notation. Additional cross-tree constraints further restrict the permitted combinations – for example, through implication rules such as HighEndGraphics ⇒ CPU_3GHz. Features can also carry attributes that define concrete data values per variant (e.g. a storage size in GB).
Example of a feature diagram: mandatory features, optional features, XOR alternatives, attributes, and a cross-tree constraint (HighEndGraphics ⇒ CPU_3GHz).
Because the formal language is clearly defined, tools can automatically check consistency and redundancy. This allows invalid feature diagrams to be detected and superfluous constraints to be identified.
When all decisions in a feature diagram are made consistently, a concrete product instance – a variant – emerges. Suitable tools support this process through a hierarchical tree view with checkboxes, automatically accounting for structural dependencies and cross-tree constraints. This prevents the creation of inconsistent configurations.
A feature diagram alone has no direct effect on requirements, architecture models, or code. The connection is established through the concept of 150% artifacts:
This principle applies to any artifact type: requirements from Codebeamer™ or DOORS™, SysML models, Office documents, or C code.
For connecting a feature model to these artifacts, there are basically two approaches: loose coupling and tight coupling. They differ above all in which errors can be detected.
In practice, loose coupling dominates today: a separate variant management tool manages feature diagrams and configurations. Presence conditions are stored in development tools as simple strings or key-value pairs. The variant management tool evaluates these and transforms the artifacts.
This approach has the advantage that the tools involved remain largely independent of each other, and the interface is narrow and can be implemented with moderate effort. However, there are some typical weaknesses:
As a consequence, errors are only detected late in the development process. Fixing them then requires considerably more effort, and the probability of defects in the final product increases.
Tight coupling requires that development artifacts are created in an environment which knows their internal structure and can be connected directly to the feature model. A language workbench meets this requirement: it allows domain-specific languages (DSLs) to be defined and domain models to be edited with projectional editors. At itemis, we use MPS by JetBrains in customer projects, among other tools. On this basis, we have developed IETS3, a powerful variant management framework which enables exactly this tight coupling and is integrated as a building block into customer-specific development tools (custom tools).
A concrete example of the added value of tight coupling is reference consistency checking in domain artifacts:
Suppose model element A references model element B via a reference Ref1. A has presence condition Cond1, B has presence condition Cond2. The reference is only consistent if the implication Cond1 ⇒ Cond2 holds – i.e., B is always present whenever A is present.
Reference consistency: if A points to B, then Cond1 ⇒ Cond2 must hold. With tight coupling, the tool checks this automatically for every reference in the model.
With tight coupling, the tool can perform this check automatically for all references in the model. If a violation is found, it computes concrete configurations as counterexamples. In practice, the model hierarchy and parent nodes are also taken into account.
With tight coupling, presence conditions are stored not as strings but as real references to features. This has several consequences:
In addition, variation conditions can be algorithmically computed (implicit conditions): if an architecture component is filtered out by its own condition, associated ports and connectors can be automatically filtered as well. This reduces the manual modeling effort, and the models remain more concise.
Tight coupling also opens up additional analysis capabilities:
Tight integration of feature models and variability-annotated development artifacts unlocks capabilities that loose coupling cannot provide: earlier error detection, reduced model complexity through implicit variation points, and domain-specific consistency checks across all variants. For the development of complex product lines, tight coupling is therefore indispensable.
Variant management and custom tooling at itemis — DSLs and tools for managing variability-rich development: Custom Tool Development →

Portalon 1.5 connects AI agents to JetBrains MPS: strong performance, broad functionality and secure deployment.
Read Article
Dr. Klaus Birken
10 min read
How the Portalon plugin connects AI coding agents like Claude to the live model of a JetBrains MPS project via MCP — structurally safe edits, validation, and language-engineering skills, on your current MPS version.
Read Article
Dr. Klaus Birken
10 min read
How Franca IDL and itemis CREATE can be integrated to validate embedded software components against interface contracts interactively during development.
Read Article
Dr. Klaus Birken
9 min read