Modeling language: Difference between revisions

Revision as of 09:45, 29 July 2025

Latest revision as of 23:15, 26 August 2025

(4 intermediate revisions by one other user not shown)

Line 1:

{{Short description|Artificial languageNotation used to expressexpressing information under a rule set}}

A '''modeling language''' is anya [[artificialnotation language]] that can be used tofor expressexpressing [[data]], [[information]] or [[knowledge]] or [[system]]s in a [[structure]] that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure of a [[programming language]].

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> A graphical modeling language uses a [[diagramming technique]] with named symbols that represent concepts and lines that connect the symbols and represent relationships and various other graphical notation to represent constraints. A textual modeling language 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]].

== 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 [[diagramming technique|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]] and [[distributed system]]s.

Line 36 ⟶ 30:

* [[SysML]] is a [[Domain-Specific Modeling]] language for [[systems engineering]] that is defined as a UML profile (customization).

* [[Unified Modeling Language]] (UML) is a [[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.

* FLINT — language which allows a high-level description of normative systems.<ref>{{Citation |lastlast1=Breteler |firstfirst1=Jeroen |title=The FLINT Ontology: An Actor-Based Model of Legal Relations |date=2023-09-11 |work=Studies on the Semantic Web |editor-last=Acosta |editor-first=Maribel |url=https://ebooks.iospress.nl/doi/10.3233/SSW230016 |access-date=2024-11-13 |publisher=IOS Press |doi=10.3233/ssw230016 |isbn=978-1-64368-424-6 |last2=van Gessel |first2=Thom |last3=Biagioni |first3=Giulia |last4=van Doesburg |first4=Robert |editor2-last=Peroni |editor2-first=Silvio |editor3-last=Vahdati |editor3-first=Sahar |editor4-last=Gentile |editor4-first=Anna-Lisa|doi-access=free }}</ref>

* [[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]] of a [[system]].

Line 85 ⟶ 79:

==== Object-oriented ====

SomeA organizationslanguage usefor them[[object-oriented extensivelymodeling]] in(OOM) combination withis a softwarenotation developmentfor methodologymodeling toa progresssystem fromas initialobject-oriented. specificationAn toorganization anmay implementationuse plan andOOM to communicatedocument thatand plandescribe tothe ansystem entirearchitecture teamand design to ofboth 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.

[[Object modeling language]]s 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 ====