Revision as of 12:15, 14 July 2021 edit 2601:5c0:c380:7700:8db7:e524:ebf1:6e7f (talk) Added the modeling language Lifecycle Modeling Language https://en.wikipedia.org/wiki/Lifecycle_Modeling_Language ← Previous edit		Revision as of 21:22, 8 September 2021 edit undo Talpedia (talk \| contribs) Extended confirmed users 4,521 edits include a source about informal diagrams, mention some more useful for informal diagrams Tag: Visual edit Next edit →
Line 108: 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 ~~not~~cannot ~~much~~be ~~else~~used programmatically.<ref>{{Cite journal\|last=Baltes\|first=Sebastian\|last2=Diehl\|first2=Stephan\|date=2014-11-11\|title=Sketches and diagrams in practice\|url=https://doi.org/10.1145/2635868.2635891\|journal=Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering\|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}}</ref>{{Rp\|539}} Executable modeling languages applied with proper tool support, however, are expected to automate system [[verification and validation]], [[simulation]] and [[Automatic programming\|code generation]] from the same representations. == Quality ==

Modeling language: Difference between revisions