Guiding Principles

  • Shape styles should be consistent for the entire enterprise and defined in advance before start modeling
    • Shape definitions can be changed by the user in the class definition table
    • Pre-defined shapes cannot be changed by the user
    • Pre-defined shape colors represent a grouping e.g. portfolio
    • Make DiagramDiagram - Drawing that illustrates or visually explains a thing or idea by outlining its component parts and the relationships among them.s visually attractive by using minimum four (4) colors
    • Avoid using too much colors
    • Add legends to the DiagramDiagram - Drawing that illustrates or visually explains a thing or idea by outlining its component parts and the relationships among them. when using colors to express indicators e.g. risk
    • Use collapsible Containers to reduce complexity in models
    • Remove not relevant artifacts from the DiagramDiagram - Drawing that illustrates or visually explains a thing or idea by outlining its component parts and the relationships among them.
    • Add a name, description, purpose, version and contact name to the DiagramDiagram - Drawing that illustrates or visually explains a thing or idea by outlining its component parts and the relationships among them. to help consumers understanding it

Updated about a month ago


Guiding Principles


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.