Modeling language: Difference between revisions

Revision as of 07:56, 9 April 2006

Revision as of 07:59, 9 April 2006

Line 5:

Although one secondary goal of modeling languages aims to support programming without programmers, historically software developers have become involved once the requirements specification is complete. Increased software complexity, particularly the ability to provide software support for concurrency requires knowledge of [[parallel computing]] and [[distributed system]]s.

A large number of modeling languages appear in the literature, however, the most notable languages are ones having the most extensive tool support. As of 20052006 these include:

* [[Unified Modeling Language]] (UML) incorporates a wide variety of diagramming techniques and topologies. Its extensive underlying tool support enables specifications written using one technique or 'view' to be transparently converted and rendered in another view, eventually resulting in executable artifacts.

Line 15:

* [[SysML]] is a modeling language, based on UML, that address the need of [[System Engineering]].

* [[ATL]] (The [[ATLAS Transformation Language]] is also a modeling language (because an ATL program is a model conforming to a precise metamodel). However this is a '''Domain Specific Modeling Language''', intended for a precise task ('''model transformation'''). This may be contrasted to the [[Unified Modeling Language]] which is a '''General Purpose Modeling Language'''. ATL is a model transformation language of the [[QVT]] family.

==See also==