JDomInO is presented, a bidirectional synchronization toolchain for tactical DDD that keeps a Java codebase and its domain model connected through a shared metamodel, with the goal of keeping the two in sync as the system evolves.
Abstract
Domain-Driven Design gives teams a shared vocabulary for complex business logic, but that vocabulary only stays useful as long as the model and the code agree with each other. In practice, they drift apart: code changes outpace the model, or model revisions never make it into the codebase. This paper presents JDomInO, a bidirectional synchronization toolchain for tactical DDD that keeps a Java codebase and its domain model connected through a shared metamodel, with the goal of keeping the two in sync as the system evolves. JDomInO generates Java code structure deterministically from a domain model (forward path) and reconstructs a domain model from existing Java code (reverse path). The forward path has been fully validated on a Hotel Management scenario covering all 12 building block types in the metamodel; the reverse path's mapping logic has passed unit testing, with end-to-end validation underway. We also outline how the structured domain model produced by JDomInO could serve as a precision context layer for AI code assistants, helping them respect aggregate boundaries and DDD semantics that raw source code alone does not convey.
Large language models generate code effectively but falter in enterprise settings that demand complex business rules, particularly in rule consistency and conflict detection. This study proposes the Atomic Logic Sheet (ALS), a structured representation of business logic, injected through the Hierarchical Business Logic...
Man-Su Kim, Museong Choi, Miseon Shim et al.· Electronics· 0 citations
Large Language Models are increasingly used to generate structured engineering artifacts, yet the instruction artifacts that govern this generation are rarely treated as modeling artifacts in their own right. They typically appear as monolithic prompt blocks, schemas, or informal examples. When tools, metamodels, APIs,...
Louis Burk, Alexander Fischer, Christoph Scharnagl et al.· Proceedings of the ACM/IEEE...· 0 citations
Evaluations of model-based engineering (MBE) typically report what a generator produces—coverage, artefacts emitted, lines generated. Yet under industrial delivery pressure much of that structure is later overwritten, bypassed, or absorbed into hand-written code, while other model-derived assets quietly endure. We argu...
Artur Boronat, Jawad Mustafa, Fola-Dami Eyitemi· Proceedings of the ACM/IEEE...· 0 citations
An airborne software development approach for manned and unmanned aerial vehicles aimed at reducing inconsistencies across system, model-based functional, and embedded software domains is presented and a repository-centered implementation to address recurring failure modes is proposed.
Nils Schlautmann, V. Sinitsyn, Benjamin Engelhard et al.· 0 citations
This paper reviews recent empirical literature to ask what the developer's job is shifting from typing code to directing agents that type code a change often summarized as a move from code generation to code orchestration.
P. N. Nesarajan, P. Thenmozhi, S. A. et al.· International Journal of Inn...· 0 citations
The paper argues, on the evidence gathered so far, that formal rules in the mathematical language of B must remain the source of truth, while the language model serves as the fenced assistant in a distributed safety-critical railway system.
Thierry Lecomte, Vincent Germain· arXiv.org· 1 citation
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.