SLACommon Sample Clauses
SLACommon. Top-level overview of the languages in the DSL, showing usage (dotted arrows) and extension (solid arrows). Because of these problems we could not use the model in its original form, but adapted it to be used in the structure of the DSL. First, the core of the model was implemented in MPS as faithfully as possible with respect to SLA*. Second, the model was adapted to use direct references. Finally, to separate concerns, the language was split up into separate sub-languages, leveraging the intrinsic composition and extension properties of MPS:
SLACommon. SLACommon is used to define common concepts, data types, and interfaces that are used in the other languages. Its purpose is to prevent duplication of concepts and unnecessary dependencies, as well as having a single place to define new data types. Figure 5.4 shows the structure of SLACommon. The most important concepts of the language are the interfaces IDescribed- Concept and Document. The former adds a description to a concept in a similar way that MPS’s interface INamedConcept add a name to a concept. The latter is an interface used to indicate that a document can be generated from that concept. Part of SLACommon was based on SLA*, but it grew during the DSL development as more shared elements were required. While this language does not specifically fulfil any requirements, it supports the other languages in doing so.