Architecture Diagrams
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
UML/StarUML diagrams illustrate design intent; executable declarations remain authoritative.
The Runtime book discusses visual modeling with UML/StarUML as an aid to design and communication, while the authoritative model still resides in accepted declarations and compiler/runtime contracts. A drawing may guide domain discussion; it is not proof that a particular plugin, UI command or editor version is supported.
Engineering rules
- Relate each diagram element to a named conceptual model element.
- Do not invent a toolbar command or installation step absent from the source.
- Use an executable validation path for metadata and runtime behavior.
- Treat tool-specific compatibility as versioned and separately testable.
Chapter outline (original LaTeX headings)
- Visual Models as Runtime Metadata Sources
- Recommended Round Trip
- Stable Identity Matters
- Model What the Runtime Can Enforce
- Validate Before Activation
- Designer and Universal MVC
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/designer-staruml-and-visual-modeling.tex.