View source for Modeling language

{{Short description|Artificial language used to express information under a rule set}}
A '''modeling language''' is any artificial language that can be used to express [[Data|data]], [[Information|information]] or [[Philosophy:Knowledge|knowledge]] or [[Philosophy:System|system]]s in a [[Structure|structure]] that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure Programing language.

== Overview ==
A modeling language can be graphical or textual.<ref>{{Cite conference |last1=He |first1=Xiao |last2=Ma |first2=Zhiyi |last3=Shao |first3=Weizhong |last4=Li |first4=Ge |title=31st Annual International Computer Software and Applications Conference - Vol. 1- (COMPSAC 2007) |date=July 2007 |chapter=A metamodel for the notation of graphical modeling languages |chapter-url=https://ieeexplore.ieee.org/document/4291008 |volume=1 |pages=219–224 |doi=10.1109/COMPSAC.2007.27|isbn=978-0-7695-2870-0 |citeseerx=10.1.1.526.5321 }}</ref>

* ''Graphical'' modeling languages use a diagram technique with named symbols that represent concepts and lines that connect the symbols and represent relationships and various other graphical notation to represent constraints.
* ''Textual'' modeling languages may use standardized keywords accompanied by parameters or natural language terms and phrases to make computer-interpretable expressions.

An example of a graphical modeling language and a corresponding textual modeling language is [[EXPRESS (data modeling language)|EXPRESS]].

Not all modeling languages are executable, and for those that are, the use of them doesn't necessarily mean that programmers are no longer required. On the contrary, executable modeling languages are intended to amplify the productivity of skilled programmers, so that they can address more challenging problems, such as [[Parallel computing|parallel computing]] and distributed systems.

A large number of modeling languages appear in the literature.

== Type of modeling languages ==

=== Graphical types ===
Example of graphical modeling languages in the field of computer science, project management and systems engineering:
* Behavior Trees are a formal, graphical modeling language used primarily in [[Engineering:Systems engineering|systems]] and [[Software engineering|software engineering]]. Commonly used to unambiguously represent the hundreds or even thousands of [[Philosophy:Natural language|natural language]] requirements that are typically used to express the [[Social:Project stakeholder|stakeholder]] needs for a large-scale software-integrated system.
* Business Process Modeling Notation (BPMN, and the [[XML]] form BPML) is an example of a Process Modeling language.
* [[Engineering:C-K theory|C-K theory]] consists of a modeling language for design processes.
* [[DRAKON]] is a [[General-purpose modeling|general-purpose algorithmic modeling]] language for specifying software-intensive systems, a schematic representation of an algorithm or a stepwise process, and a family of [[Programming language|programming language]]s.
* [[EXPRESS (data modeling language)|EXPRESS]] and EXPRESS-G (ISO 10303-11) is an international standard general-purpose [[Data modeling|data modeling]] language.
* [[Finance:Extended Enterprise Modeling Language|Extended Enterprise Modeling Language]] (EEML) is commonly used for business process modeling across a number of layers.
* [[Flowchart]] is a schematic representation of an algorithm or a stepwise process.
* Fundamental Modeling Concepts (FMC) modeling language for software-intensive systems.
* [[IDEF]] is a family of modeling languages, which include [[IDEF0]] for functional modeling, [[IDEF1X]] for information modeling, [[IDEF3]] for business process modeling, [[IDEF4]] for Object-Oriented Design and [[IDEF5]] for modeling ontologies.
* Jackson Structured Programming (JSP) is a method for structured programming based on correspondences between data stream structure and program structure.
* LePUS3 is an object-oriented visual Design Description Language and a [[Formal specification|formal specification]] language that is suitable primarily for modeling large object-oriented ([[Java (programming language)|Java]], [[C++]], [[C Sharp (programming language)|C#]]) programs and design patterns.
* [[Lifecycle Modeling Language]] is an open-standard language for [[Engineering:Systems engineering|systems engineering]] that supports the full system lifecycle: conceptual, utilization, support and retirement stages.
* Object-Role Modeling (ORM) in the field of software engineering is a method for conceptual modeling, and can be used as a tool for information and rules analysis.
* [[Petri net]]s use variations on exactly one diagramming technique and topology, namely the [[Bipartite graph|bipartite graph]].  The simplicity of its basic user interface easily enabled extensive tool support over the years, particularly in the areas of model checking, graphically oriented simulation, and software verification.
* Southbeach Notation is a visual modeling language used to describe situations in terms of agents that are considered useful or harmful from the modeler's perspective. The notation shows how the agents interact with each other and whether this interaction improves or worsens the situation.
* [[Specification and Description Language]] (SDL) is a specification language targeted at the unambiguous specification and description of the behavior of reactive and distributed systems.
* SysML is a Domain-Specific Modeling language for [[Engineering:Systems engineering|systems engineering]] that is defined as a UML profile (customization).
* [[Unified Modeling Language]] (UML) is a [[General-purpose modeling|general-purpose modeling]] language that is an industry standard for specifying software-intensive systems. UML 2.0, the current version, supports thirteen different diagram techniques, and has widespread tool support.
* [[Service-oriented modeling#Service-oriented modeling framework|Service-oriented modeling framework (SOMF)]] is a holistic language for designing enterprise and application level architecture models in the space of enterprise architecture, virtualization, service-oriented architecture (SOA), cloud computing, and more.<ref name="Bell">{{cite book |last=Bell |first=Michael|title=Service-Oriented Modeling: Service Analysis, Design, and Architecture|url=https://archive.org/details/serviceorientedm0000bell |url-access=registration |year= 2008 |publisher=Wiley & Sons|isbn=978-0-470-14111-3 |chapter=Introduction to Service-Oriented Modeling}}</ref>
* [[Architecture description language]] (ADL) is a language used to describe and represent the [[Systems architecture|systems architecture]] of a [[Philosophy:System|system]].
* Architecture Analysis & Design Language (AADL) is a modeling language that supports early and repeated analyses of a system's architecture with respect to performance-critical properties through an extendable notation, a tool framework, and precisely defined semantics.

Examples of graphical modeling languages in other fields of science.
* [[EAST-ADL]] is a  Domain-Specific Modeling language dedicated to automotive system design.
* [[Energy Systems Language]] (ESL), a language that aims to model ecological energetics & global economics.
*[[IEC 61499]] defines Domain-Specific Modeling language dedicated to distribute industrial process measurement and control systems.

=== Textual types ===
Information models can also be expressed in formalized natural languages, such as Gellish.<ref>* Andries van Renssen, [http://www.gellish.net/downloads/file/10-phd-gellish-a-generic-extensible-ontological-language.html Gellish, A Generic Extensible Ontological Language] {{webarchive|url=https://web.archive.org/web/20121130015036/http://www.gellish.net/downloads/file/10-phd-gellish-a-generic-extensible-ontological-language.html |date=2012-11-30 }}, Delft University of Technology, 2005.</ref> Gellish has natural language variants such as Gellish Formal English and Gellish Formal Dutch (Gellish Formeel Nederlands), etc. Gellish Formal English is an information representation language or semantic modeling language that is defined in the Gellish English Dictionary-Taxonomy, which has the form of a Taxonomy-Ontology (similarly for Dutch). Gellish Formal English is not only suitable to express knowledge, requirements and dictionaries, taxonomies and ontologies, but also information about individual things. All that information is expressed in one language and therefore it can all be integrated, independent of the question whether it is stored in central or distributed or in federated databases. Information models in Gellish Formal English consists of collections of Gellish Formal English expressions, that use natural language terms and formalized phrases. For example, a geographic information model might consist of a number of Gellish Formal English expressions, such as:

 - the Eiffel tower <is located in> Paris
 - Paris <is classified as a> city

whereas information requirements and knowledge can be expressed for example as follows:

 - tower <shall be located in a> geographical area
 - city <is a kind of> geographical area

Such Gellish Formal English expressions use names of concepts (such as "city") and phrases that represent relation types (such as {{angbr|is located in}} and {{angbr|is classified as a}}) that should be selected from the Gellish English Dictionary-Taxonomy (or of your own domain dictionary). The Gellish English Dictionary-Taxonomy enables the creation of semantically rich information models, because the dictionary contains more than 600 standard relation types and contains definitions of more than 40000 concepts. An information model in Gellish can express facts or make statements, queries and answers.

=== More specific types ===
In the field of [[Computer science|computer science]] recently more specific types of modeling languages have emerged.

==== Algebraic ====
[[Software:Algebraic modeling language|Algebraic Modeling Languages]] (AML) are high-level programming languages for describing and solving high complexity problems for large scale mathematical computation (i.e. large scale optimization type problems). One particular advantage of AMLs like [[Social:AIMMS|AIMMS]], [[Software:AMPL|AMPL]], [[Software:General Algebraic Modeling System|GAMS]], [[Software:Gekko (optimization software)|Gekko]], [[Software:FICO Xpress|Mosel]], OPL and [[OptimJ]] is the similarity of its syntax to the mathematical notation of optimization problems. This allows for a very concise and readable definition of problems in the domain of optimization, which is supported by certain language elements like sets, indices, algebraic expressions, powerful sparse index and data handling variables, constraints with arbitrary names. The algebraic formulation of a model does not contain any hints how to process it.

==== Behavioral ====

Behavioral languages are designed to describe the observable behavior of complex systems consisting of components that
execute concurrently. These languages focus on the description of key concepts such as: concurrency, nondeterminism, synchronization, and communication. The semantic foundations of Behavioral languages are [[Process calculus|process calculus]] or process algebra.

==== Discipline-specific ====
A [[Service-oriented modeling#Discipline-specific modeling|discipline-specific modeling (DspM)]] language is focused on deliverables affiliated with a specific software development life cycle stage. Therefore, such language offers a distinct vocabulary, syntax, and notation for each stage, such as discovery, analysis, design, architecture, contraction, etc. For example, for the analysis phase of a project, the modeler employs specific analysis notation to deliver an analysis proposition diagram. During the design phase, however, logical design notation is used to depict relationship between software entities. In addition, the discipline-specific modeling language best practices does not preclude practitioners from combining the various notations in a single diagram.

==== Domain-specific ====
[[Domain-specific modeling]] (DSM) is a software engineering methodology for designing and developing systems, most often IT systems such as computer software. It involves systematic use of a graphical [[Domain-specific language|domain-specific language]] (DSL) to represent the various facets of a system. DSM languages tend to support higher-level abstractions than General-purpose modeling languages, so they require less effort and fewer low-level details to specify a given system.

==== Framework-specific ====
A [[Framework-specific modeling language|framework-specific modeling language]] (FSML) is a kind of domain-specific modeling language which is designed for an object-oriented application framework. FSMLs define framework-provided abstractions as FSML concepts and decompose the abstractions into features. The features represent implementation steps or choices.

A FSML concept can be configured by selecting features and providing values for features. Such a concept configuration represents how the concept should be implemented in the code. In other words, concept configuration describes how the framework should be completed in order to create the implementation of the concept.

==== Information and knowledge modeling ====
[[Linked data]] and [[Ontology engineering|ontology engineering]] require 'host languages' to represent [[Entity–relationship model|entities and the relations between them]], [[Constraint (mathematics)|constraints]] between the properties of entities and relations, and [[Metadata|metadata]] [[Attribute (computing)|attributes]]. [[JSON-LD]] and [[Resource Description Framework|RDF]] are two major (and semantically almost equivalent) languages in this context, primarily because they support [[Resource Description Framework#Statement reification and context|statement reification and contextualisation]] which are essential properties to support the [[Philosophy:Higher-order logic|higher-order logic]] needed to reason about models. [[Model transformation]] is a common example of such reasoning.

==== Object-oriented ====
Object modeling languages are modeling languages based on a standardized set of symbols and ways of arranging them to model (part of) an object oriented software design or system design.

Some organizations use them extensively in combination with a software development methodology to progress from initial specification to an implementation plan and to communicate that plan to an entire team of developers and stakeholders. Because a modeling language is visual and at a higher-level of abstraction than code, using models encourages the generation of a shared vision that may prevent problems of differing interpretation later in development. Often software modeling tools are used to construct these models, which may then be capable of automatic translation to code.

==== Virtual reality ====
[[VRML|Virtual Reality Modeling Language]] (VRML), before 1995 known as the Virtual Reality Markup Language is a standard file format for representing 3-dimensional (3D) interactive vector graphics, designed particularly with the World Wide Web in mind.

==== Others ====
* Architecture Description Language
* [[Face Modeling Language]]
* [[Generative Modelling Language]]
* [[Java Modeling Language]]
* [[Promela]]
* Rebeca Modeling Language
* [[Service Modeling Language]]
* [[Web Services Modeling Language]]
* [[X3D]]

== Applications ==
Various kinds of modeling languages are applied in different disciplines, including [[Computer science|computer science]], [[Information management|information management]], [[Finance:Business process modeling|business process modeling]], [[Software engineering|software engineering]], and [[Engineering:Systems engineering|systems engineering]]. Modeling languages can be used to specify:
* system requirements,
* structures and
* behaviors.
Modeling languages are intended to be used to precisely specify systems so that stakeholders (e.g., customers, operators, analysts, designers) can better understand the system being modeled.

The more mature modeling languages are precise, consistent and executable. Informal diagramming techniques applied with drawing tools are expected to produce useful pictorial representations of system requirements, structures and behaviors, which can be useful for communication, design, and problem solving but cannot be used programmatically.<ref>{{Cite book|last1=Baltes|first1=Sebastian|last2=Diehl|first2=Stephan|title=Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering |chapter=Sketches and diagrams in practice |date=2014-11-11|chapter-url=https://doi.org/10.1145/2635868.2635891|series=FSE 2014|location=Hong Kong, China|publisher=Association for Computing Machinery|pages=530–541|doi=10.1145/2635868.2635891|isbn=978-1-4503-3056-5|arxiv=1706.09172|s2cid=2436333 }}</ref>{{Rp|539}} Executable modeling languages applied with proper tool support, however, are expected to automate system [[Engineering:Verification and validation|verification and validation]], [[Simulation|simulation]] and [[Automatic programming|code generation]] from the same representations.

== Quality ==
A review of modelling languages is essential to be able to assign which languages are appropriate for different modelling settings. In the term settings we include stakeholders, domain and the knowledge connected. Assessing the '''language quality''' is a means that aims to achieve better models.

=== Framework for evaluation ===
Here language quality is stated in accordance with the [[SEQUAL framework]] for quality of models developed by Krogstie, Sindre and Lindland (2003), since this is a framework that connects the language quality to a framework for general model quality. Five areas are used in this framework to describe language quality and these are supposed to express both the conceptual as well as the visual notation of the language. We will not go into a thoroughly explanation of the underlying quality framework of models but concentrate on the areas used to explain the language quality framework.

==== Domain appropriateness ====
The framework states the ability to represent the domain as domain appropriateness. The statement ''appropriateness'' can be a bit vague, but in this particular context it means ''able to express''. You should ideally only be able to express things that are in the domain but be powerful enough to include everything that is in the domain. This requirement might seem a bit strict, but the aim is to get a visually expressed model which includes everything relevant to the domain and excludes everything not appropriate for the domain. To achieve this, the language has to have a good distinction of which notations and [[Philosophy:Syntax|syntax]]es that are advantageous to present.

==== Participant appropriateness ====
To evaluate the participant appropriateness we try to identify how well the language expresses the knowledge held by the stakeholders. This involves challenges since a stakeholder's knowledge is subjective. The knowledge of the stakeholder is both tacit and explicit. Both types of knowledge are of dynamic character. In this framework only the explicit type of knowledge is taken into account. The language should to a large extent express all the explicit knowledge of the stakeholders relevant to the domain.

==== Modeller appropriateness ====
Last paragraph stated that knowledge of the stakeholders should be presented in a good way. In addition it is imperative that the language should be able to express all possible explicit knowledge of the stakeholders. No knowledge should be left unexpressed due to lacks in the language.

==== Comprehensibility appropriateness ====
Comprehensibility appropriateness makes sure that the social actors understand the model due to a consistent use of the language. To achieve this the framework includes a set of criteria. The general importance that these express is that the language should be flexible, easy to organize and easy to distinguish different parts of the language internally as well as from other languages. In addition to this, the goal should be as simple as possible and that each symbol in the language has a unique representation.

This is in connection to also to the structure of the development requirements. 
.

==== Tool appropriateness ====
To ensure that the domain actually modelled is usable for analyzing and further processing, the language has to ensure that it is possible to reason in an automatic way. To achieve this it has to include formal syntax and semantics. Another advantage by formalizing is the ability to discover errors in an early stage. It is not always that the language best fitted for the technical actors is the same as for the social actors.

==== Organizational appropriateness ====
The language used is appropriate for the organizational context, e.g. that the language is standardized within the organization, or that it is supported by tools that are chosen as standard in the organization.

== See also ==
{{Div col|colwidth=22em}}
* {{Annotated link |AltaRica}}
* {{Annotated link |Analogical models}}
* {{Annotated link |Anthropomorphism}}
* {{Annotated link |Data model}}
* {{Annotated link |Data modeling}}
* {{Annotated link |Metamodeling}}
* [[Model-based testing]] (MBT)
* {{Annotated link |Model-driven architecture}}
* [[Model-driven engineering]] (MDE)
* {{Annotated link |Modeling perspective}}
* {{Annotated link |Ontology language}}
* {{Annotated link |Pseudocode}}
* {{Annotated link |Scientific modelling}}
* {{Annotated link |Service-oriented modeling}}
* {{Annotated link |Visual modeling}}
* {{Annotated link |Visual programming language}}
{{Div col end}}

== References ==
{{Reflist}}

== Further reading ==
* [[Biography:John Krogstie|John Krogstie]] (2003) [http://www.igi-global.com/chapter/evaluating-uml-using-generic-quality/30534 "Evaluating UML using a generic quality framework"] . SINTEF Telecom and Informatics and IDI, NTNU, Norway
* Krogstie and Sølvsberg (2003). ''Information Systems Engineering: Conceptual Modeling in a Quality Perspective''. Institute of computer and information sciences.\
* Anna Gunhild Nysetvold and [[Biography:John Krogstie|John Krogstie]] (2005). [http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-363/paper15.pdf "Assessing business processing modeling languages using a generic quality framework"]. Institute of computer and information sciences.

== External links ==
* [http://www.fmc-modeling.org/ Fundamental Modeling Concepts]
* [http://modeling-languages.com/ Software Modeling Languages Portal]
* [http://www-verimag.imag.fr/~async/bip.php BIP -- Incremental Component-based Construction of Real-time Systems]
* [http://www.gellish.net/ Gellish Formal English]

{{Computer science}}
{{Software engineering}}
{{Computer language}}

[[Category:Specification languages]]
[[Category:Modeling languages| ]]

{{Sourceattribution|Modeling language}}