Based on my awareness the textual UML tools market is one of the fastest-growing segment in the UML tools market. They provide some kind of lightweight solution to draw some models.
I feel Development staff should feel more comfortable with textual languages than with graphical ones.
I am not familiar with textual UML. But as you describe it as lightweight, the following might be of use.
If it is used for conceptual models, just exploring and defining particular concepts, a light version would normally do. Then the audience are probably not developers or programmers.
If you need it for logical models, e.g. to define data elements, names, use unique concept codes, express data types, external value sets, units etc. And to carefully define relationships. You need to check the capabilities of the UML tool.
If you need it to fully define a full stack appli
full stack application that covers design, development and testing and next implementation of solutions, then stay away from light tools. Eg if you use RM-ODP or similar.
I use Sparx Enterprise Architect for conceptual and logical models. It is fine, but getting more difficult to use every new version.
They are very convenient as plugins to be used in the transformation of Requirement Techniques, since they can be easily connected with programming platforms like Java.
A researcher has send me the following link which gives a good introduction to textual modeling tools.
https://modeling-languages.com/text-uml-tools-complete-list/
I have been using graphical UML tools since 1996. While there are some cases where text can better communicate requirements and design constraints, graphical modeling is generally superior for the majority of requirements and design specifications. OCL is text and can be a good way to express certain constraints.
Here are some references to support the preference of graphics over text.
Larkin, J. H., Simon, H. A.: Why a Diagram is (Sometimes) Worth Ten Thousand Words. Cognitive Science 11, 1 (1987), 36 – 44 (1987)
Moody, D. L.: The ‘Physics’ of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering. IEEE Transactions on Software Engineering 35, 6 (2009) https://doi.org/10.1109/TSE.2009.67 (2009)
Moody, D. L., van Hillegersberg, J.: Evaluating the Visual Syntax of UML: An Analysis of the Cognitive Effectiveness of the UML Family of Diagrams. In 1st International Conference on Software Language Engineering. Springer-Verlag, Berlin, Germany, 16 – 34. https://doi.org/10.1007/978-3-642-00434-6 LNCS 5452 (2009)
Just to clarify, I am an industry person and my graphical UML modeling was done in industry projects and in several OMG standards.
Dan Matheson , Thanks for your Answer. they say
- Using Text to UML tools is a Faster way to create your models.
- textual modeling tools have a very low barrier to entry
- programmers typically feel more comfortable with textual languages than with
graphical ones
- helps blind software engineers to design and read UML diagrams.
https://modeling-languages.com/text-uml-tools-complete-list/
- Badges
- Science topic