Why a textual notation, what is wrong with the graphical one?
Short answer: the TextUML Toolkit is a tool for creating well-formed detailed UML models that will serve as input to code generation. A textual notation works better for describing and showing the details, whereas the graphical notation is more suited for providing an overview of the system (see next question). Long answer: please read this.
Related Questions
- When choosing flights using the graphical interface, the colored flight bars display is all messed up. Whats wrong?
- What is the relationship between semantic, domain, notation, and graphical definition models?
- What is the relationship between semantic, domain, notation, and graphical definition models?
- Can a tool that uses a textual notation be considered UML compliant?
- Can a tool that uses a textual notation be considered UML compliant?
- Why a textual notation, what is wrong with the graphical one?