Revision as of 17:12, 2 October 2022 edit Skyerise (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 149,364 edits →See also: related orphaned article which should be integrated ← Previous edit		Revision as of 05:28, 19 November 2022 edit undo Citation bot (talk \| contribs) Bots 5,870,405 edits Add: s2cid, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. \| Use this bot. Report bugs. \| Suggested by BorgQueen \| Category:Specification languages \| #UCB_Category 26/50 Next edit →
Line 109: 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. [[Technical Drawing#Applications\|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 journal\|~~last~~last1=Baltes\|~~first~~first1=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\|arxiv=1706.09172\|s2cid=2436333 }}</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