Content deleted Content added
grammar fix |
Arctic Rhino (talk | contribs) No edit summary |
||
Line 1:
{{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]], [[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
== Overview ==
Line 70:
==== 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 the 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 the systematic use of a graphical [[___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 ====
| |||