it architecture questions to be asked - netclose › web › wp-content › uploads ›...

1© 2010 Cisco and/or its affiliates. All rights reserved.

IT Architecturequestions to be askedBeat Baumberger IT Infra Architect

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

Strategic Initiatives

TechnologyResponses

Architectures

Systems

Products ( Solutions )

Business

Architecture

Architecture

alignment

dialog

Business

Priorities

IT Techn.

Architecture

Partners and

Vendors


• Do I have a consistent access policy architecture across my network for all users?

• Can mobile devices access my network transparently and securely?

• Can my network deliver real time collaboration experience?

• Am I using my network to reduce my energy cost?

• Can I secure my assets on premise and in the cloud?

• Can my network optimize performance of applications no matter where users are and how they are connected?

• Is my network ready for current and future regulatory requirements?


Architecture

Building Blocks

Components

Abstract Capabilities

Relationships

Simplification

Layer 3 Edge Module

Wired Access

ModuleWireless Access

Architecture

Core Routing Module

Infrastructure

Services Access

Module

Design

Best Solution

Correct Product

Performance

Scaling


A

Architecture

Vision

B

Business

Architecture

C

Information

Systems

Architecture

D

Technology

Architecture

EOpportunities

& Solutions

FMigration

Planning

GImplementation

Governance

HArchitecture

Change

Management

Requirements

Management

Preliminary

Preliminary Phase

- Framework and Principles

- Confirm stakeholders

- Define scope

B) Business Architecture

- Describe existing business arch.

- Develop target business arch.

- Analyze GAP

C) Inf. Systems Architecture

- Develop target arch. for Data and

Application domain

D) Technology Architecture

- Develop a target techn. Arch. That

will support the business requirements

- basis of implementation work

A) Architecture Vision

- Management commitment

- Validate business principles

- Set the scope

Source: www.TOGAF.com


BorderlessApplication

And NetworkServices

A

P

L

Awareness

Participation

Leadership

Cisco Engagement

A

P

A

P

L

L

A

A

A


Applications

Infra

stru

ctu

re

Borderless End-Point/User Experience

Mobility Security Performance

Borderless Network Services

Security:TrustSec

Performance Assurance

MobilityVideo: Medianet

Green:EnergyWise

Common Services MulticastQoSRouting

CRMVideo

SurveillanceTelePresence Collaboration

( e.g. WebEX )

Design

InfrastructureLayer

PlatformLayer

ApplicationLayer

10© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID

Borderless Network Architecture

Infrastructure

Borderless End-Point/User Services

Mobility WorkplaceExperience

Video

AnyConnect, Mobile Collaboration

Borderless Network ServicesBorderless

Management and Policy

Switching

Wireless

WAAS

Routing

Security

Mobility:Motion

Security:TrustSec

Video: Medianet

Green:EnergyWise

PROFESSIONAL SERVICES: Products to Systems to Architectures

Enabling a Borderless Performance Experience

Application Performance: AppVelocity


Change

Frequency View Description Typical Consumers

Conceptual provides the highest level of abstraction. It defines the overall vision supporting the architecture and describes the fundamental principles that will be used for future IT decisions. It must be closely aligned with the business vision.

Logical is also called the “Target Architecture”. It

includes actionable engineering blueprints that

differentiate approaches and provide a set of product

independent architectures for IT components not fully

defined. It also includes a set of standards for

Technology Domains.

Physical provides the highest level of detail, and is

also called the “Implementable Architecture”. It

includes physical engineering diagrams, detailed

designs, “buy-lists” and recommendations regarding

the implementation of technology solutions and

associated processes and tools.

Low

High

Conceptual

Architecture

Vendor Agnostic

Logical

Architecture

Standard Selection

Physical

Architecture

High Level Design

Low Level Design

Implementation

Specifics

Executive Management

Business Planners

Technical Peers in other

domains

Optimisation and TOCVendor/Product Agnostic

Vendor/Product Specific

IT Strategists and

Enterprise Architects

Technical Peers in other

domains

Design and Engineering

Design and Engineering

Network and IT Delivery

Network and IT Delivery

Optimisation and TOC

Risk Management


Information Technology (IT) principles provide guidance on the use

and deployment of all IT resources and assets across the enterprise.

They are developed in order to make the information environment as

productive and cost-effective as possible.

Recommended Format for Defining Principles

Name Should both represent the essence of the rule as well as

be easy to remember.

Statement Should succinctly and unambiguously communicate the

fundamental rule.

Rationale Should highlight the business benefits of adhering to the

principle, using business terminology.

Implications Should highlight the requirements, both for the business

and IT, for carrying out the principle - in terms of

resources, costs, and activities/tasks.

Source: www.TOGAF.com


Name Statement Rationale Implication

Consolidation

Network

Segregation

Network Access

Unified Fabric

Energy Efficiency

Wireless

Application

Visibility


BusinessArchitecture

IT Technology Architecture

IT Engineering

IT Operation

IT Service CatalogArchitecturealignment

dialogPartners and Vendors

Platformas a Service

Infrastructureas a Service

Softwareas a Service

Public Cloud

Peers

Business userswill purchase services directly from the CSP service catalogLittle or zero touch with the IT department

Governance,

IT Service

Management,

Architecture

Thank you.

it architecture questions to be asked - netclose › web › wp-content › uploads ›...

Documents