1. International Research and Development Institute Uyo
A Domain Specific Modeling Language (DSML) Semantic Model for Artefact Orientation
Japheth R. Bunakiye
Dept. of Mathematics/Computer Science
Faculty of Science, Niger Delta University,
Wilberforce Island, Nigeria
Co-Author: Ogheneove E. Edward
Department of Computer Science, Faculty of Science,
University of Port Harcourt, Nigeria.
Eighth African Regional Conference on New Strategies for Sustainable Development
International Research and Development Institute Uyo
May, 2015.
                  A Domain Specific Modeling Language (DSML) Semantic Model for Artefact Orientation by Japheth Bunakiye Richard is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

2. The Emphasis:
This is a research work on the development of a domain specific modeling language (DSML) for modeling oil and gas pipeline systems.
To create a semantic mapping of concepts in the oil and gas pipeline application domain to a language formalism with some levels of abstraction. So that pipeline systems modeling can be achieved on easily, productively and on time.
Definition: Domain specific modelling languages are any artificial language that can be used to express information or knowledge systems in a structure that is defined by a consistent set of rules [Bernhard et al. 35th IEEE Annual Computer Software and Applications Conference 2011] .

3. The Concept of a Semantic Model
Generally, semantics is the assignment of meanings to sentences. Mathematicians use meanings like numbers and functions, programmers favour machine actions, musicians prefer audible tones, and so on. Semantics in this context means "from the user's perspective."
A semantic model in software engineering also means the following:
It is a conceptual model in which semantic information is included.
The model describes the meaning of its instances.
A semantic data model is an abstraction that defines how the stored symbols ( i.e. the instance data) relate to the real world.

4. Example Pipeline Model [AutoCAD Objects]
Fig.1: Pipeline Model
These pipeline models as shown in figure 1 actually forms the instance of the semantic model.

5. The Semantic Definitions
The semantics are defined in the sense of oil and gas pipeline product line model (PPM).
Fig.2: Feature Model
A product (P) of the feature model holds information regarding a set of leaves. The model (M) holding values of products as a subset of primitive nodes, and the constraints (C) are the rules guiding the specific definitions.
𝐴 𝑃𝑃𝑀 𝑖𝑠 𝑎 𝑡𝑟𝑖𝑝𝑙𝑒 𝑃, 𝑀, 𝐶
𝑊ℎ𝑒𝑟𝑒:
𝑃= 𝑝₁, 𝑝₂, 𝑝₃, , 𝑝ₑ∈𝑃 𝑖𝑠 𝑡ℎ𝑒 𝑠𝑒𝑡 𝑜𝑓 𝑙𝑒𝑎𝑣𝑒𝑠 𝑃=𝑝(𝐹)
 𝑀=𝑚 ∈𝑀 𝑖𝑠 𝑡ℎ𝑒 𝑠𝑢𝑏𝑠𝑒𝑡 𝑜𝑓 𝑡ℎ𝑒 𝑛𝑜𝑑𝑒𝑠 𝑜𝑓 𝑡ℎ𝑒 𝐹𝐷:𝑀=𝑝𝑁
𝐶= 𝜙∈Φ;𝑎𝑟𝑒 𝑡ℎ𝑒 𝑠𝑎𝑡𝑖𝑠𝑓𝑦𝑎𝑏𝑙𝑒 𝑐𝑜𝑛𝑠𝑡𝑟𝑎𝑖𝑛𝑡𝑠

6. 𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛 1
𝑇ℎ𝑒 𝑝𝑟𝑜𝑑𝑢𝑐𝑡 𝑙𝑖𝑛𝑒 𝑤𝑖𝑡ℎ 𝑎 𝑠𝑒𝑡 𝑜𝑓 𝑓𝑒𝑎𝑡𝑢𝑟𝑒 𝑙𝑒𝑎𝑓𝑠 𝐹 𝑜𝑓 𝑡ℎ𝑒 𝑃𝑃𝑀 𝑖𝑠 𝑎 𝑣𝑎𝑙𝑖𝑑 𝑚𝑜𝑑𝑒𝑙 𝑚∈𝑀 𝑖𝑓𝑓:
(𝑎)𝑇ℎ𝑒 𝑐𝑜𝑛𝑐𝑒𝑝𝑡 𝑖𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑚𝑜𝑑𝑒𝑙: 𝑟 ∈ 𝑚
𝑏 𝑖. 𝐼𝑓 𝑎 𝑥𝑜𝑟− 𝑛𝑜𝑑𝑒 𝑖𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑚𝑜𝑑𝑒𝑙, 𝑒𝑥𝑎𝑐𝑡𝑙𝑦 𝑜𝑛𝑒 𝑜𝑓 𝑖𝑡𝑠 𝑠𝑢𝑏 𝑓𝑒𝑎𝑡𝑢𝑟𝑒𝑠 𝑖𝑠: 𝑞∈𝑚
⇒∃!𝑛.𝑞 → 𝑛 ⋀ 𝑛 ∈𝑚
𝑖𝑖. 𝐼𝑓 𝑎 𝑎𝑛𝑑−𝑛𝑜𝑑𝑒 𝑖𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑚𝑜𝑑𝑒𝑙, 𝑎𝑙𝑙 𝑖𝑡𝑠 𝑠𝑢𝑏𝑓𝑒𝑎𝑡𝑢𝑟𝑒𝑠 𝑎𝑟𝑒: 𝑘 ∈ 𝑚
⇒∀𝑛.(𝑘 → 𝑛 ⇒ 𝑛 ∈𝑚)
𝑐 𝑖. 𝑇ℎ𝑒 𝑚𝑜𝑑𝑒𝑙 𝑚𝑢𝑠𝑡 𝑠𝑎𝑡𝑖𝑠𝑓𝑦 𝑡ℎ𝑒 𝑐𝑜𝑛𝑠𝑡𝑟𝑎𝑖𝑛𝑡 𝑠𝑒𝑡: ∀𝜙∈Φ,𝑚⊨𝜙
𝑤ℎ𝑒𝑟𝑒:
𝑚⊨𝑛₁ 𝑚𝑢𝑡𝑒𝑥 𝑛₂ → 𝑛₁ 𝑎𝑛𝑑 𝑛₂∉𝑚;
𝑚⊨𝑛₁ 𝑟𝑒𝑞𝑢𝑖𝑟𝑒𝑠 𝑛₂ → 𝑛₁𝑛₂∈𝑚
𝑖𝑖. 𝑆𝑎𝑡𝑖𝑠𝑓𝑦 𝑡ℎ𝑒 𝑡𝑒𝑥𝑡𝑢𝑎𝑙 𝑐𝑜𝑛𝑠𝑡𝑟𝑎𝑖𝑛𝑡𝑠: ∀𝜙∈Φ,𝑚⊨𝜙,
𝑤ℎ𝑒𝑟𝑒 𝑚⊨𝜙₁→𝑝₁∈𝑚⇒𝑝₂∈𝑚 𝑖𝑠 𝑡𝑟𝑢𝑒
𝑖𝑖𝑖. 𝑆𝑎𝑡𝑖𝑠𝑓𝑦 𝑡ℎ𝑒 𝑔𝑟𝑎𝑝ℎ𝑖𝑐𝑎𝑙 𝑐𝑜𝑛𝑠𝑡𝑟𝑎𝑖𝑛𝑡𝑠:∀ 𝑛₁∗𝑛₂ ∈𝐶, ∗ 𝑛₁∈𝑚,𝑛₂∈𝑚 𝑖𝑠 𝑡𝑟𝑢𝑒

7. 𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛2
𝑇ℎ𝑒 𝑝𝑟𝑜𝑑𝑢𝑐𝑡 𝑙𝑖𝑛𝑒 𝑃 𝑤𝑖𝑡ℎ 𝑎 𝑠𝑒𝑡 𝑜𝑓 𝑓𝑒𝑎𝑡𝑢𝑟𝑒 𝑙𝑒𝑎𝑓𝑠 𝐹 𝑜𝑓 𝑡ℎ𝑒 𝑃𝑃𝑀 𝑖𝑠 𝑡ℎ𝑒 𝑠𝑒𝑡 𝑜𝑓 𝑙𝑒𝑎𝑣𝑒𝑠
𝑃=𝑝(𝐹) 𝑖𝑓𝑓:
(𝑎)𝑇ℎ𝑒 𝑝𝑟𝑜𝑑𝑢𝑐𝑡 𝑙𝑖𝑛𝑒 𝑖𝑠 𝑎 𝑠𝑒𝑡 𝑜𝑓 𝑝𝑟𝑜𝑑𝑢𝑐𝑡𝑠: 𝑝(𝑃) = 𝑝(𝑝(𝐹)).
𝑏 𝑇ℎ𝑒 𝑝𝑟𝑜𝑑𝑢𝑐𝑡 𝑙𝑖𝑛𝑒 𝑖𝑠 𝑡ℎ𝑒 𝑝𝑟𝑜𝑑𝑢𝑐𝑡𝑠 𝑜𝑓 𝑡ℎ𝑒 𝑃𝑃𝑀𝑠 𝑣𝑎𝑙𝑖𝑑 𝑚𝑜𝑑𝑒𝑙𝑠:
𝑠𝑢𝑐ℎ 𝑡ℎ𝑎𝑡 𝑝 = {𝑚∩ 𝐹∖𝑚 ⊨𝑝}
(𝑐)𝐴 𝑝𝑟𝑜𝑑𝑢𝑐𝑡 𝑘 𝑖𝑠 𝑎 𝑠𝑒𝑡 𝑜𝑓 𝑝𝑟𝑖𝑚𝑖𝑡𝑖𝑣𝑒 𝑛𝑜𝑑𝑒𝑠: 𝑘∈𝑝(𝑃).
The domain model incorporates all of the communication abstractions and their relationships. The semantics units within the abstraction layers in the domain model are precisely defined to capture concurrency so that the systems should meet the requirements of the operating environment.

8. Semantic Model Specifications 1
𝐷𝑒𝑓𝑖𝑛𝑒 𝑃𝑝𝑒𝑙𝑖𝑛𝑒𝐵𝑢𝑖𝑙𝑑 𝑃𝑎𝑟𝑎𝑚𝑒𝑡𝑒𝑟𝑠
𝑏𝑢𝑖𝑙𝑑_𝑝𝑖𝑝𝑒 {
𝑐𝑜𝑚𝑝𝑜𝑛𝑒𝑛𝑡 = (); (𝑑𝑜𝑢𝑏𝑙𝑒)
𝑓𝑖𝑡𝑡𝑖𝑛𝑔 = (); (𝑑𝑜𝑢𝑏𝑙𝑒)
𝑗𝑜𝑖𝑛𝑡 = (); (𝑑𝑜𝑢𝑏𝑙𝑒)
𝑠𝑢𝑝𝑝𝑜𝑟𝑡 = (); (𝑑𝑜𝑢𝑏𝑙𝑒)
𝑎𝑛𝑔𝑙𝑒 = (); (𝑑𝑜𝑢𝑏𝑙𝑒)
𝑠𝑖𝑧𝑒 = (); (𝑑𝑖𝑎𝑚𝑒𝑡𝑒𝑟_𝑖𝑛𝑛𝑒𝑟(𝑓𝑙𝑜𝑎𝑡))
(𝑑𝑖𝑎𝑚𝑒𝑡𝑒𝑟_𝑜𝑢𝑡𝑒𝑟(𝑓𝑙𝑜𝑎𝑡))
(𝑤𝑖𝑑𝑡ℎ(𝑖𝑛𝑡))
(𝑡ℎ𝑖𝑐𝑘𝑛𝑒𝑠𝑠(𝑖𝑛𝑡))
𝑢𝑛𝑖𝑡𝑠 = (); (𝑖𝑛𝑡)
𝑝𝑜𝑖𝑛𝑡_𝑥 = (); (𝑖𝑛𝑡)
𝑝𝑜𝑖𝑛𝑡_𝑦 = (); (𝑖𝑛𝑡)
𝑝𝑜𝑖𝑛𝑡_𝑧 = (); (𝑖𝑛𝑡)
}}𝑝𝑖𝑝𝑒_𝑗𝑜𝑖𝑛.𝑚𝑒𝑡ℎ𝑜𝑑.𝑡ℎ𝑖𝑠𝑝𝑖𝑝𝑒.𝑝(0,1)
The operational mode is hinged on the description of the grammar content of the input parameters in the formal notations. Figure 3 is a hypothetical pipeline build event that is carried out in real life. It is a problem solving venture that minimizes the complexities encountered in the engineering design workplace.
Fig. 3: Fragments of Pipeline Build Grammar
𝐵𝑢𝑖𝑙𝑑 𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐸𝑞 𝐵𝑢𝑖𝑙𝑑
𝑆𝑖𝑧𝑒 𝐸𝑞 𝐷𝑖𝑚𝑒𝑛𝑠𝑖𝑜𝑛
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∗
𝐸𝑛𝑑 𝐼𝑑
𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐵𝑢𝑖𝑙𝑑 𝑚𝑒𝑡𝑟𝑖𝑐𝑠∶:= 𝑠ℎ𝑎𝑝𝑒|𝑑𝑖𝑟𝑒𝑐𝑡𝑖𝑜𝑛|𝑐𝑜𝑚𝑝𝑜𝑛𝑒𝑛𝑡|𝑓𝑖𝑡𝑡𝑖𝑛𝑔𝑠|𝑗𝑜𝑖𝑛𝑡|𝑠𝑢𝑝𝑝𝑜𝑟𝑡
𝐸𝑞∶:= "="
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∶:= 𝐵𝑢𝑖𝑙𝑑𝑒𝑟 𝐼𝑑
𝑃𝑜𝑖𝑛𝑡 𝐸𝑞 𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛
𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛∶:= 𝑜𝑟𝑖𝑔𝑖𝑛|𝑎𝑡𝑡𝑟𝑖𝑏𝑢𝑡𝑒𝑠|𝑙𝑒𝑛𝑔𝑡ℎ|𝑠𝑙𝑜𝑝𝑒|𝑡𝑒𝑟𝑚𝑖𝑛𝑎𝑙
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛𝑠∶:= 𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∗
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∶:= 𝐷𝑒𝑓𝑖𝑛𝑒 𝐼𝑑 𝑆ℎ𝑎𝑝𝑒 ; 𝑊𝑖𝑑𝑡ℎ 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟;𝑇ℎ𝑖𝑐𝑘𝑛𝑒𝑠𝑠 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟

9. Semantic Model Specifications 2
𝐵𝑢𝑖𝑙𝑑 𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐸𝑞 𝐵𝑢𝑖𝑙𝑑
𝑆𝑖𝑧𝑒 𝐸𝑞 𝐷𝑖𝑚𝑒𝑛𝑠𝑖𝑜𝑛
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∗
𝐸𝑛𝑑 𝐼𝑑
𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐵𝑢𝑖𝑙𝑑 𝑚𝑒𝑡𝑟𝑖𝑐𝑠∶:= 𝑠ℎ𝑎𝑝𝑒|𝑑𝑖𝑟𝑒𝑐𝑡𝑖𝑜𝑛|𝑐𝑜𝑚𝑝𝑜𝑛𝑒𝑛𝑡|𝑓𝑖𝑡𝑡𝑖𝑛𝑔𝑠|𝑗𝑜𝑖𝑛𝑡|𝑠𝑢𝑝𝑝𝑜𝑟𝑡
𝐸𝑞∶:= "="
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∶:= 𝐵𝑢𝑖𝑙𝑑𝑒𝑟 𝐼𝑑
𝑃𝑜𝑖𝑛𝑡 𝐸𝑞 𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛
𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛∶:= 𝑜𝑟𝑖𝑔𝑖𝑛|𝑎𝑡𝑡𝑟𝑖𝑏𝑢𝑡𝑒𝑠|𝑙𝑒𝑛𝑔𝑡ℎ|𝑠𝑙𝑜𝑝𝑒|𝑡𝑒𝑟𝑚𝑖𝑛𝑎𝑙
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛𝑠∶:= 𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∗
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∶:= 𝐷𝑒𝑓𝑖𝑛𝑒 𝐼𝑑 𝑆ℎ𝑎𝑝𝑒 ; 𝑊𝑖𝑑𝑡ℎ 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟;𝑇ℎ𝑖𝑐𝑘𝑛𝑒𝑠𝑠 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟
Fig.4: Formal Notations in BNF
For the DSML to implement its core operations, figure 3 is showing the creation of the grammar fragments in BNF notation for defining the various pipeline build metrics of the language.
𝐵𝑢𝑖𝑙𝑑 𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐸𝑞 𝐵𝑢𝑖𝑙𝑑
𝑆𝑖𝑧𝑒 𝐸𝑞 𝐷𝑖𝑚𝑒𝑛𝑠𝑖𝑜𝑛
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∗
𝐸𝑛𝑑 𝐼𝑑
𝑃𝑖𝑝𝑒𝑙𝑖𝑛𝑒 𝐵𝑢𝑖𝑙𝑑 𝑚𝑒𝑡𝑟𝑖𝑐𝑠∶:= 𝑠ℎ𝑎𝑝𝑒|𝑑𝑖𝑟𝑒𝑐𝑡𝑖𝑜𝑛|𝑐𝑜𝑚𝑝𝑜𝑛𝑒𝑛𝑡|𝑓𝑖𝑡𝑡𝑖𝑛𝑔𝑠|𝑗𝑜𝑖𝑛𝑡|𝑠𝑢𝑝𝑝𝑜𝑟𝑡
𝐸𝑞∶:= "="
𝐵𝑢𝑖𝑙𝑑𝑒𝑟∶:= 𝐵𝑢𝑖𝑙𝑑𝑒𝑟 𝐼𝑑
𝑃𝑜𝑖𝑛𝑡 𝐸𝑞 𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛
𝑃𝑜𝑠𝑖𝑡𝑖𝑜𝑛∶:= 𝑜𝑟𝑖𝑔𝑖𝑛|𝑎𝑡𝑡𝑟𝑖𝑏𝑢𝑡𝑒𝑠|𝑙𝑒𝑛𝑔𝑡ℎ|𝑠𝑙𝑜𝑝𝑒|𝑡𝑒𝑟𝑚𝑖𝑛𝑎𝑙
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛𝑠∶:= 𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∗
𝐷𝑒𝑓𝑖𝑛𝑖𝑡𝑖𝑜𝑛∶:= 𝐷𝑒𝑓𝑖𝑛𝑒 𝐼𝑑 𝑆ℎ𝑎𝑝𝑒 ; 𝑊𝑖𝑑𝑡ℎ 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟;𝑇ℎ𝑖𝑐𝑘𝑛𝑒𝑠𝑠 𝐸𝑞 𝑁𝑢𝑚𝑏𝑒𝑟

10. Semantic Model Specifications 3
𝑒𝑣𝑒𝑛𝑡
𝑛𝑎𝑚𝑒: 𝑒𝑙𝑏𝑜𝑤𝐽𝑜𝑖𝑛𝑡
𝑐𝑜𝑑𝑒: 𝑃𝑖𝑝𝑒𝐵𝑖𝑢𝑙𝑑
𝑒𝑛𝑑
𝑠𝑡𝑎𝑡𝑒: 𝑎𝑐𝑡𝑖𝑣𝑒
𝑒𝑙𝑏𝑜𝑤𝐽𝑜𝑖𝑛𝑡 → 𝑊𝑎𝑖𝑡𝑖𝑛𝑔𝐹𝑜𝑟𝑃𝑎𝑟𝑎𝑚𝑒𝑡𝑒𝑟𝑠
𝑠𝑡𝑎𝑡𝑒: 𝑗𝑜𝑖𝑛.𝑡ℎ𝑖𝑠.𝑒𝑙𝑏𝑜𝑤
𝑡𝑟𝑎𝑛𝑠𝑙𝑎𝑡𝑒 → 𝑡𝑎𝑟𝑔𝑒𝑡
𝑡𝑎𝑟𝑔𝑒𝑡: 𝑛𝑎𝑚𝑒 → 𝑗𝑜𝑖𝑛.𝑡ℎ𝑖𝑠.𝑒𝑙𝑏𝑜𝑤
𝑡𝑟𝑖𝑔𝑔𝑒𝑟: 𝑒𝑙𝑏𝑜𝑤𝐽𝑜𝑖𝑛𝑡
In the domain model is the semantic model subset consisting of the classes of the events and their relationships with a focus on the user’s perspectives. Figure 5 is an example of a typical event pertaining to user’s perspective. The relationships are how the fundamental engineering principles are linked to produce a total life cycle approach to pipelines system design and operation.
Fig.5: Semantic Model (User’s Perspective)

11. Figure 7b: Modelling Editor
Discussion 1: Semantic Model Representation
The resultant effect of the internal working mechanism is that the DSML interpreter program (i.e. the event handler DSML scripts) runs as a layer over the semantic model (i.e. the library framework) and populates it. Illustrated in figure 6 is the semantic representation, it is the in-memory object model with the state of events of the same input metrics that our DSML describes.
Figure 7a: User Control
Figure 7b: Modelling Editor

12. Discussion 2: Object Binder Code Snippet
In the context of our DSML, the semantic model representation has clearly indicated the data binding process to be an object binder that specifies the event states.

13. Discussion 3: Template Transformation
The events become more vivid as a template transformation made it possible for the functionality of a new text editing platform i.e. the creation of the editor.

14. Discussion 4: UI Text Editor
. Discussion of results
After the template transformation. What happens is that the components container binds the data source from the internal representations to the DSML model, particularly to the root node of the model resulting to the creation of the editor.

15. THANK YOU SO MUCH
                  A Domain Specific Modeling Language (DSML) Semantic Model for Artefact Orientation by Japheth Bunakiye Richard is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

16. QUESTIONS?