sym12 27h

Talking Architecture: A Framework of Frameworks: 

Loran Naugher Bill Rosser Talking Architecture: A Framework of Frameworks These materials can be reproduced only with Gartner’s official approval. Such approvals may be requested via e-mail -- quote.requests@gartner.com.

New Enterprise Architecture Framework — the Time Is Now: 

New Enterprise Architecture Framework — the Time Is Now Our traditional architecture models cannot support the concept of the zero-latency enterprise and won't survive in this new era of business process outsourcing, Web services, joint R&D, portals, e-hubs, integration brokers and quick partnerships that must be reconstituted almost on the fly as business needs change and evolve.

Key Issues: 

Key Issues What key elements define the enterprise architecture framework? How does your enterprise architecture framework position your business for a multienterprise, connected future? What additional artifacts of architecture do you need to move your definitions from one layer to the next? How will you communicate the benefits and content of your architecture, gain compliance, deal with exceptions and keep the architecture revitalized through an evergreening process?

Gartner’s New Enterprise Architecture Framework: 

Enterprise The Multienterprise Grid Business Process Styles Patterns Bricks Gartner’s New Enterprise Architecture Framework What key elements define the enterprise architecture framework?

Define Your Technology Grid — Your Business Playing Field: 

Architecture vision & scope IT strategy What business wants What IT has to do Business strategy Enterprise requirements Customer requirements Supplier requirements Other stakeholders What Architecture has to do How does your EA framework position your business for a multienterprise, connected future?  Define Your playing field Objectives Competitive advantage Speed of implementation Dynamic service selection High security Lower total costs  Develop Document your own — Logical grid Defined meanings (semantics) Define Your Technology Grid — Your Business Playing Field

From One Plane to the Next ...: 

From One Plane to the Next ... To move from the "grid" to "styles" Business drivers IT drivers Principles Operational business models Business process models To move from "styles" to "patterns" Business function models Information flow maps Pattern creation / adoption To move from "patterns" to "bricks" “As-is” and “to-be” configurations Taxonomy and consensus workshops What additional artifacts of architecture do you need to move your definitions from one layer to the next? Although the grid, styles, patterns and bricks are the key control planes, an enterprise architecture needs additional definition to transition from one plane to the next.

Define Your Enterprise’s Business Drivers and IT Drivers : 

Define Your Enterprise’s Business Drivers and IT Drivers Improve quality Decrease time to market Enable product innovation Support effective cross selling Transform business processes Improve organizational efficiency Integrate across multiple delivery channels Meet regulatory issues or legislative mandates Ease transitions during mergers or acquisitions Provide a unified customer view across business lines Support transactions with partners, suppliers and customers Align IT with business Connect disparate systems Minimize TCO Re-platform/modernize Leverage existing skills Leverage the legacy investment Consolidate multiple centers/servers Integrate the back-end applications Minimize application complexity Minimize enterprise complexity Improve availability Improve scalability

Slide8: 

Principles are: established rules that guide technology decision-making. Principles are based on values and beliefs; they provide the foundation on which architectural designs are built and to which appeal can be made in the event of differing views on particulars. Criteria for Architectural Principles Understandable To people throughout the Enterprise; Clear interpretation of concept and intent Complete and Consistent No major omissions No duplication, overlap, or contractions Long-lasting Independent of technology, who, where, when, policies & procedures Interpretation may change with the times, but not the words Types of Architectural Principles Overarching Guiding Principles Management Architecture Principles Business Architecture Principles Application Architecture Principles Data Architecture Principles Infrastructure Architecture Principles Security Architecture Principles Create IT Architectural Principles

Your Operational Business Model and Process Model Leads You to Styles: 

Your Operational Business Model and Process Model Leads You to Styles

Business Process Styles Have Varying Characteristics: 

Business Process Styles Have Varying Characteristics

Business Function Models and Flow Maps Lead to Patterns : 

Business Function Model Business Function Models and Flow Maps Lead to Patterns Information Flow Model

Patterns: Block Diagrams of Ways to Implement Technology Styles: 

Patterns: Block Diagrams of Ways to Implement Technology Styles Midrange HTTP Server Midrange Web Application Server User Interface Layer Intranet Business Logic Layer Data Access Layer Business/ Application Logic Data Logic DB SAMPLE 3-TIER TRANSACTION PROCESSING PATTERN More detail about implementation choices for the chosen standard set of patterns would then be reflected in what we call configurations. Examples: workstations, midrange application servers, enterprise application servers, firewalls and LANs.

How Many Computing Styles, Patterns/Configurations?: 

How Many Computing Styles, Patterns/Configurations? The common set of architecture domains apply to each style and pattern, then the enterprise architecture development process helps you reach consistency and standardization of the lower-level subdomains, elements and bricks. Architecture domains

Define Standards and Products as 'Bricks' of Technology: 

Define Standards and Products as 'Bricks' of Technology Architecture “Bricks” Each architecture component is subdivided into a set of specific elements. Each technology element is discussed based on industry status and outlook. The status is based on availability of standards (e.g., formal or de facto, vendors and products — emerging and deployed).

Grid Position: Styles, Patterns, Configurations, Bricks, Evergreening: 

Grid Position: Styles, Patterns, Configurations, Bricks, Evergreening Transaction Processing Design Pattern Baseline Environment Tactical Deployment Strategic Direction Retirement Targets Containment Targets Mainstream Systems Emerging Trends Technology Issues Implications/Dependencies Brick for Element “x” Specifications/Standards Copyright © 2002 Evergreening and Governance Processes - tied to Gartner Research and Consulting

What Is IT Governance?: 

What Is IT Governance? IT governance defines the cross-jurisdictional organizational structure that provides a decision making process to determine the services, architecture, standards and policies for the enterprise’s IT A management process of setting goals and establishing policies, practices, procedures and organizational structure to provide reasonable assurance that enterprise goals will be met An improvement tool that provides vital input for continuous improvement of business processes, controls and key performance indicators to measure outcomes and reset objectives How will you communicate the benefits and content of your architecture?

Integrate Architecture Into Overall IT Management Process: 

Drives Supported by Improved by Influences Integrate Architecture Into Overall IT Management Process

Sell Benefits of an Architecture — and Beware of Potential Problems: 

Sell Benefits of an Architecture — and Beware of Potential Problems Benefits of an IT architecture Reduces cost Improves interoperability Aids scalability Enables agility Improves security Eases staffing Reduces technical risk Potential problems Expense and effort Tensions Uncertain justification Updating commitment Supports business innovation

Your Business Priorities Determine Your Next Steps: 

Your Business Priorities Determine Your Next Steps Determine your priorities, whether it’s your position on the grid, what styles you need, what standard patterns you should deploy or what bricks will determine your buy list, then take the steps to move from one plane to the next. To move from the “grid” to “styles” Business drivers IT drivers Principles Operational business models Business process models To move from “styles” to “patterns” Business function models Information flow maps To move from “patterns” to “bricks” Configurations Models And, integrate your architecture governance processes into overall IT management processes and structures