SAHM

This site uses cookies to improve your experience and analyze visits.

Accept
Decline
Learn more about cookies
SAHM logo
  • Home
  • About
  • Pricing
  • Knowledge Hub
  • Support
  • Book a Meeting
  • Customer Portal
  • Employee Portal
  • Contact
Menu

Language

Services

Digital TransformationEnterprise ArchitectureNORA ComplianceEA Tool ImplementationPricing

Expertise

TOGAF FrameworkDGA NORAAvolution ABACUSIT Strategy

Company

About UsContact Us

Resources

Schedule ConsultationRequest DemoCustomer SupportSubmit Ticket

Get in touch

info@sahm.sa+966 53 113 0434

2023 - 2026 © SAHM Information Technology. All Rights Reserved. | Riyadh, Saudi Arabia

Back to Guides

EA Views

Guideline for developing EA views: defining types, detail levels, and providing examples for entities.

Overview

  • Views present EA components in different formats based on purpose and audience.
  • Based on building blocks, attributes, and relationships in the general component model.
  • Help manage and document current and target states in the EA tool.

View Types

TypeDescriptionUsesExamples
CatalogLists EA components with attributes and related building blocks.Technical purposes, reference guides, large component inventories.Service catalog, application catalog
MatrixShows relationships between components where one can link to many.Change impact analysis, decision support.App/business service, org units/services
VisualShows relationships between components through visual representation.Executive overview, supports communication and discussion.Application map

Detail Levels

Three Levels
Conceptual

Highest level. Focuses on general concepts and basic requirements. Examples: business value chain, application map.

Logical

More detail than conceptual. Focuses on moderate detail of attributes and relationships. Examples: integration map, network diagram.

Physical

Most detailed. Focuses on full component details. Examples: data vault catalog, virtual server catalog.

Stakeholder Sharing Methodology

StepDescription
Identify RequirementsIdentify stakeholder requirements and needs from various departments.
Design ViewsDesign views per stakeholder segment requirements.
Define ChannelsDefine communication channels for sharing views or granting tool access.
Version GovernanceControl version updates based on stakeholder feedback.
Continuous ImprovementOngoing review and feedback collection to ensure needs are met.

Key Takeaway

Views support decision-making and raise awareness of EA components among all stakeholder categories, from senior management to development and design teams.

Related Topics

General Component Model

Six EA Domains

EA Reports

EA Views | Development Guide | NORA | SAHM