https://docs.rosetta-technology.io/rosetta/rune-dsl/Recent content in Rune DSL on Rosetta DocumentationHugo -- gohugo.ioen© Copyright {year} [REGnosys Ltd](https://regnosys.com) | [Privacy Statement](https://regnosys.com/regnosys-privacy-statement) | [Terms of Use](https://regnosys.com/regnosys-terms-of-use)Mon, 07 Feb 2022 17:26:23 +0000https://docs.rosetta-technology.io/rosetta/rune-dsl/overview/Wed, 09 Feb 2022 00:38:25 +0900https://docs.rosetta-technology.io/rosetta/rune-dsl/overview/Rune DSL ¶ Continuous Integration: Rune DSL is a Domain-Specific Language (DSL) that supports the modelling of operational processes for the financial markets’ industry. Its purpose is to promote consistency and inter-operability between the various implementations of these processes. In software engineering, a domain model is a conceptual model of a business domain that incorporates both data and logic (i.e. rules and processes). The key idea behind the Rune DSL is that, whilst financial markets’ operational infrastructure is largely electronified, many of its underlying IT systems tend to operate in silos.https://docs.rosetta-technology.io/rosetta/rune-dsl/rune-modelling-component/Fri, 01 Sep 2023 12:57:00 +0200https://docs.rosetta-technology.io/rosetta/rune-dsl/rune-modelling-component/Rune Modelling Components ¶The Rune DSL can express eight types of model components: Data Meta-Data Expression (or logic) Data Validation (or condition) Function Namespace Mapping (or synonym) Reporting Function Overriding This documentation details the purpose and features of each type of model component and highlights their relationships. Examples drawn from the Demonstration Model, a sandbox model of the “vehicle” domain, will be used to illustrate each of those features. Data Component ¶The Rune DSL provides four components to represent data in a model:https://docs.rosetta-technology.io/rosetta/rune-dsl/rune-java-documentation/Fri, 01 Sep 2023 12:57:00 +0200https://docs.rosetta-technology.io/rosetta/rune-dsl/rune-java-documentation/Rune Java Documentation ¶Types and enums ¶Structure of Generated Model Classes ¶When a Rune model is compiled, each type defined in the model is translated into a Java class that implements the RosettaModelObject interface. These generated classes follow a consistent structure: Immutable Objects: The generated classes are immutable. Once created, their state cannot be changed. Builder Pattern: Each class comes with a nested builder class that implements the RosettaModelObjectBuilder interface. The builder is used to construct instances of the class.https://docs.rosetta-technology.io/rosetta/rune-dsl/rosetta-code-generators/Wed, 09 Feb 2022 00:38:25 +0900https://docs.rosetta-technology.io/rosetta/rune-dsl/rosetta-code-generators/Rosetta Code Generators ¶Continuous Integration: License: Apache 2.0 JavaDoc: Coming soon Do you want to adopt a technical standard expressed as a domain model in the Rune DSL, but in a language other than the default (Java) distribution? You can use this guide to write your own code generator in the language of your choosing. Pre-reqs ¶This project uses JDK 21. Why Code Generation? ¶The power of distributing a technical standard as a domain model is that you do not have to re-implement that technical standard in your particular language.