Enterprise Architecture Modeling Guidelines

Enterprise Architecture Modeling Guidelines

• A model provides answers to specific business, application, and technology questions.
• Distinguish between the model and its visualization. A model is a conceptual representation; a visualization is its visual form.
• Models should be dynamic, including aspects likely to change over time.
• Models should be concise, representing only relevant concepts and relations.
• Use recognizable concepts and structures with stakeholder-appropriate names and types.
• Maintain consistency in models. Use the same terms for similar concepts across models.
• Model similar relations similarly.
• Maintain consistent levels of abstraction.
• Ensure models are complete, accurate, and correct.
• Use design viewpoints aligned with objectives.
• Include only elements contributing to modeling objectives.
• Avoid irrelevant elements.
• Make models self-explanatory.
• Separate internal and external behaviors.
• Collect feedback from stakeholders.
• Use enterprise architecture layers and phases for grouping.

Guidelines for Readability and Usability

• Internal Composition: Model elements starting with their internal structure.
• External Support: Model elements moving upwards to show what supports them.
• Realization: Direction towards how elements are realized by other elements.
• Peer Cooperation: Model elements showing interactions with related elements.
• Visual Complexity Reduction: Reduce concepts, elements, and relations in a model.

Gestalt Theory (Human Perception)

• Proximity: Related items are placed together.
• Similarity: Similar items are grouped.
• Continuity: Suggests lines continue.
• Closure: Incomplete shapes are perceived as complete.
• Common Fate: Moving or acting alike triggers perception of a group.

Layouts and Symbols

• Layouts: Basic patterns, alignment, spacing, symbol density, distinguish normal from exceptions.
• Symbols: Match real-world characteristics; use similar shapes for similar concepts.
• Directionality: Time dependencies from left to right. Avoid crossing lines.
• Line Width: Highlight important relations using thicker lines.

Use of Color

• Use color for similarity and to convey emotions, avoiding too many colors.
• Prior knowledge influences interpretations of color.

Use of Text

• Use domain-specific terminology.
• Use proper naming conventions.
• Text clarifies interpretations and associations.