Using Architecture Principles Execute Better and More Consistently Bob Hensle Director Global Enterprise Architecture Program September 29, 2014 Copyright

Using Architecture PrinciplesExecute Better and More Consistently

Bob HensleDirectorGlobal Enterprise Architecture ProgramSeptember 29, 2014

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |


Program Agenda

IT Strategy and Architecture from Oracle

Capabilities

Architecture Principles

Summary

To Learn More

1

2

3

4

5


IT Strategy and Architecture from Oracle (ITSAO)


• Helps define your Enterprise Architecture• Includes example capabilities and architecture

principles• Provides business alignment and traceability

• Helps define your Solution Architecture• Defines and organizes technology capabilities• Defines architecture principles• Includes many “perspectives”

– SOA, BPM, Cloud, Business Analytics,…

Architecture Levels

Oracle Enterprise Architecture Framework Oracle Reference Architecture


Ca-pa-bi-li-ty: is the ability of an entity (organization, person, system) to perform a function or activity to achieve or support specific objectives of the organization.

Capability

Capabilities

Defines what is required to achieve the organization’s goals and objectives

Drivers for architecture requirements Architecture delivers capabilities Gap analysis determines what capabilities

are missing


•One of the most powerful uses of capabilities is to provide traceability to business strategy.

•Provides justification for why an architecture capability is needed.

•Supports prioritization and funding decisions for IT initiatives.

Architecture Capabilities Provide Traceability

Information Architecture

Capability

ApplicationArchitecture

Capability

TechnologyArchitecture

Capability

Business Capability

ITCapability

Drives need

Influences

InfluencesInfluences

Business Strategy

Drives need

Supports

IT Initiatives

Drives


Capabilities Traceability Example

•Common way to illustrate traceability of AIT to Business

•Focuses on what needs to change to support the Business Strategy

•The AIT capabilities usually require new IT initiatives


Using Capabilities to Define an ArchitectureApplicable to both Enterprise and Solution Architectures

Architecture Reference Model

Capability Reference Model

Structure Capabilities

Capability Catalog

CompanyCapability Detail

Describes

Capability Maturity ModelEva

luates

Requirements

Capability Model


Capability CatalogArchitecture Reference Model

Combining Capability Models

Information Capabilities Framework

ORACLEORA Information

Management

Capability Reference Model

Structure Capabilities

CompanyCapability Detail

Describes

Capability Maturity ModelEva

luates

Requirements

Capability Model


Capabilities from ORA Information Management•Conceptual level

architecture provides the reference model

•High-level capabilities model illustrates the top-level capabilities

•Top-level capabilities are further broken down into second-level capabilities

•Capabilities are described in detail


Ar-chi-tec-turePrin-ci-ple: is an unequivocal statement that articulates fundamental and enduring rules that are seldom amended, used to define, model, and execute an architecture strategy and blueprint.

Architecture Principle


Rules for how architecture delivers capabilities

Provides a common set of directions, rather than leaving each architecture decision as an independent undertaking

Governance ensures that architecture adheres to principles

Differs from Guidelines


•One of the most powerful uses of principles is to provide traceability for architectural decisions.

•Principles help justify and explain particular elements or features of an architecture.

•Answers the question: “Why are we doing it this way?”

Architecture Principles Provide Traceability

Information Architecture

Principle

ApplicationArchitecture

Principle

TechnologyArchitecture

Principle

Business Architecture

Principle

ITPrinciple

Drives need

Influences

InfluencesInfluences

Business Strategy

Drives need

Influences

Architectural Decisions

Drives


Architecture PrinciplesExamples for Enterprise Architecture

Application Architecture• Common Use Applications• Technology Independence• Ease of Integration• Maximize the Effectiveness of the End

User• Adherence to Open Standards

Business Architecture• Operating Model• Enable Dynamic Business Strategy• Customer Intimacy• Product Leadership• Cost Optimization• Corporate Environment Responsibility

Information Architecture• Information Asset Management• Value and Risk Classification• Common Data Definition and

Vocabulary• Data Quality• Secure Data Sharing and Publishing

Technology Architecture• Platform Standardization• Virtualization• Availability• Performance and Scalability• Service Level Objectives• Service Encapsulation


Example Architecture PrincipleBusiness Architecture

Name Product LeadershipType Business Architecture

Statement The core value differentiator of the enterprise will be based on providing best and most innovative products to the customers.

Rationale

Top quality visionary products brought to the market in an efficient agile manner shall help in key customer acquisitions.

Breakthrough products will help leapfrog competition and open up new markets and opportunities.

Implications

Managing Product Leadership and Innovation will have to address four important processes:o Opportunity identification for new products and serviceso Management process for Research and Development portfolioo Process for design and development of the productso Go-to-market process for new products and services

Source: TOGAF


Architecture PrinciplesExamples from the Oracle Reference Architecture

Security• Defense in Depth• Least Privilege• Security as a Service• Secure Web Services• Active Threat Detection and Analysis• Complete Secure Audit Trail

Information Management• Treat All Data as an Asset• Separation of Concerns• Volume and Velocity• Information Accessibility• Information Abstraction• Unified View of Information

Service-Oriented Integration• Logical Data Representations• Normalized Data Formats• Technical Orchestrations• Opaque Service Implementation• Location Transparency• Graceful Service Migration

Business Analytics• Unified View of Information• Consistent and Complete Information• Universal Information Access• Multi-Modal Architecture• Integrated Analysis• Insight to Action


Example Architecture PrincipleInformation Architecture

Name Treat All Data As an AssetType Information Management

Statement Data are an enterprise strategic asset which must be appropriately governed and managed.

Rationale To support operational requirements and informed decision making, users, business

processes, services, and systems require controlled access to the right information at the right time using the right tools.

Implications

All structured and un/semi-structured data must be seen belonging to the enterprise and not to an individual application or business unit.

Architecture must support an active and continuous upstream and downstream governance program rather than a passive downstream information governance program.

The enterprise must define and implement an information governance and quality program with a supporting architecture.

The architecture must support easy but secure access to data regardless of where it is stored or what format it is.

Information must be provisioned with the business user/business function in mind.

Source: ORA Information Management


Architecture PrinciplesWhat Makes a Good Architecture Principle?

• Understandable• Consensus Driven• Significant• Drives and supports traceability• Stable• Documented, Published, Promoted, and Mandated• Supports consistent architecture decision making


Architecture Principles Map Example


Architecture Principles Map Example

Support Rapid Acquisitions

Back Office Functions Must Be Optimized for Cost

Improve Customer Intimacy

All Business Functions Must Be

Measured

Non-Core Processes Must Be

Standardized

Common Use ERP Applications

CRM Must Support Social Networking between Business

and Customers

Applications Must Integrate with

Enterprise Performance Mgmt

Back Office Must Support Common

Data Definition

Customer Data Must Support Social

Media

Back Office Must Maintain Master

Data Record

Must Support Standard Data

Exchange Formats

Standardized Technology Platform

Service-Oriented Architecture

Adherence to Open Standards

SLA-Driven Performance

Busi

ness

Appl

icati

onIn

form

ation

Tech

nolo

gies


Shift Investment from Support to Innovation



Architecture Principles and Objectives Matrix



• Architecture Principles provide the rules on how to deliver capabilities• Architecture Principles provide traceability back to business concerns• Architecture Principles need to be enforced

– This is why governance is vital– Variances can be allowed as an exception case

• Architecture Principles ensure a consistent, cogent architecture– Provide a consistent set of “directions” for architecture decisions– Alternative is a “Frankentecture”

Summary


To Learn More• Visit www.oracle.com/goto/itstrategies

• Visit www.oracle.com/technetwork/architect

• Visit www.oracle.com/us/solutions/enterprise-architecture

• Blog along with Oracle Enterprise Architects at blogs.oracle.com/enterprisearchitecture

• Get certified in IT Architecture

• Send us feedback at [email protected]

• Contact your Oracle Account Team


Safe Harbor StatementThe preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.



Architecture PrinciplesSteps to Capture Architecture Principles

Identify Drivers

Determine relevant drivers such as goals, objectives, issues, and risks

ValidatePrinciples

Relevant stakeholders formally acceptdocumented principles

DefinePrinciples

Collaboratively define name, statement, rationale, and implications

PrioritizePrinciples

Prioritize principles in the context of “all other things being equal”

Classify & Relate

Principles

Classify against the appropriate dimensions and define relationships

Documents

Using Architecture Principles Execute Better and More Consistently Bob Hensle Director Global Enterprise Architecture Program September 29, 2014 Copyright