EA Problems & Solutions

Enterprise Architectures (Giorgio de Chirico)

EA Engineering & Capabilities

The primary objective of enterprise architecture (EA) is to bring business, organization, and systems under a single governance roof. Whatever the acronyms on that roof, what is at stake is a balancing act between business and systems concerns, the former driven by shifting and competitive environments, the latter by the sustainability of assets and capabilities. That put issues on two perspectives:

  • The business perspective considers the continuity and integrity of symbolic representations across domains and along time.
  • The architectural perspective is focused on the alignment of enterprise organization and systems with business strategic and operational objectives.

To that end, core EA issues must be identified that could be used to define stereotypes and patterns.

Enterprise Architecture Core Issues

At the enterprise level architecture patterns should provide reliable solutions to architectural issues without delving into the specifics of business domains and/or systems design. That can be achieved with three key taxonomies focused on EA issues:

  • The nature of the footprint of objects and activities: business, symbolic, physical
  • EA behavior with regard to environment: passive, reactive, proactive
  • The nature of communication and collaboration between environment, organization, and systems: digital, symbolic, natural
Core EA Issues

The first part will expound core architectural issues and stereotypes using the OWL kernel introduced in EA in bOwls.

EA Core Stereotypes

The second will consider the consistency of options, the third will introduce basic patterns.

Enterprise Architecture Patterns

Taking advantage of the Pagoda blueprint, the aim of EA patterns is to combine these perspectives using templates defined in terms of anchors, domains, and use cases:

  • Anchors, for the mapping of enterprise architecture to business objects identified in the environment
  • Domains, for the integrity and consistency of symbolic representations across organizational units
  • Use cases, for the interactions between systems and environments
Engineering
Capabilities

%d bloggers like this: