Enterprise Architecture Patterns Overview

Enterprise Architecture Patterns and Anti-patterns

• Enterprise Architecture Patterns (EAPs) are reusable design solutions for common architectural problems
• They help avoid repeating past mistakes
• EAPs have a consistent structure, starting with a descriptive name and problem definition
• Examples include layered and client-server patterns

The Pattern Catalog

• Categorizes patterns into Business, Infrastructure, and Support
• Patterns within each category can use or provide interfaces to other patterns
• O-shaped connectors represent provided interfaces and U-shaped connectors represent usage of an interface

Types of Patterns

• Business Patterns: Directly related to core business processes, use depends on specific industry (e.g., finance, healthcare)
• Support Patterns: Related to typical support functions, including human resources, finance, and logistics
• Infrastructure Patterns: Provide essential, often invisible services for all patterns, crucial for effective operation

Enterprise Architecture Pattern (EAP) Example

• Visual diagram illustrating a client-server architecture with components (e.g., client, server, broker, models) and interactions
• Layer structure is depicted with various components within those layers

Single Sign-On (SSO) Example

• SSO is an access control method for multiple software systems
• Users can access the entire system with a single ID, provided over an IP network
• Diagram shows interconnected systems (e.g., business applications, portals, workflow engines) using SSO

Web and EJB Operations Example

• Diagram describes general operation process of web and EJB elements
• Web elements depend on database resources and notice management interacts with numerous related databases

Anti-patterns

• Anti-patterns are flawed solutions to common problems, potentially making the situation worse
• Examples include:
  • Donkey in a tiger skin: implementing an EA initiative without relevant groundwork
  • Zealotry: excessive focus on theoretical EA over practical implementation
  • Process without people: creating processes without considering responsible parties
  • Non-political: ignoring organizational politics during program creation

Dell IT Transformation

• Dell, a major computer manufacturer, broadened into IT services
• Rhonda Gass leads IT strategy, using a three-year roadmap based on Enterprise Architecture (EA)
• Significant investments are included in the roadmap across numerous programs (Global Quote to Cash, Global Service Delivery, etc.)

Creeping Diversity Problem

• Dell's expansion into software involved acquiring companies with diverse systems
• Integrating these systems created inconsistencies and difficulties
• Existing systems made adaptation for new capabilities impossible; required a more focused and organized approach

Rationalization (Planning) Process

• Dell's IT infrastructure rationalization focused on standardizing diverse systems
• Process included understanding the current state of IT and business processes and aligning them
• Enterprise vision blueprint guided projects, defining strategy, goals, and objectives

Driven by Architecture

• Dell's current approach emphasizes logical, cross-domain processes, unlike prior emphasis on physical processes
• Teams focus on core process areas (e.g., Develop, Market, Sell, Fulfill, Support) to enhance customer value chain

Future State Reference Architecture

• Dell has created a comprehensive and detailed model/blueprint for their future state architecture.
• Diagram displays visual representations of various systems (e.g., inventory, disposition applications) and their connections.

Creating Business/IT Alignment

• Dell aligns IT investments with reference architecture prioritizing highest return
• Architecture review boards ensure consistent implementation and adherence to established standards
• Periodic review ensures projects are on track toward a three-year reference architecture goal

Process Center of Excellence (COE)

• COE emphasizes process-driven approach to transformation
• Focuses on key areas for development, market, sell, fulfill, and support across an organization.
• Includes business priorities, and interdependencies between processes.

This quiz explores the essential concepts of Enterprise Architecture Patterns (EAPs) and their categorization into business, infrastructure, and support patterns. Understand the consistent structures and examples of patterns while learning about their roles in avoiding architectural mistakes.