MEIE881

Architecture and Infrastructure

Architecture & Infrastructure Define: client/server, server, thick client, thin client,

mainframe, legacy system, peer-to-peerDistinguish architecture from infrastructureDiscuss the relationship between strategy, business

requirements, architecture, and infrastructureDiscuss the applicability of evaluation criteria to

architecture and infrastructureAnalyze infrastructure and architecture needs across

hardware, software, data and networksDescribe the purpose and steps in Business Continuity

PlanningDefine and describe SOA

Who needs IT Architecture and Infrastructure?

Strategy, Requirements, Architecture & Infrastructure

Strategy

Business Requirements

Architecture

Infrastructure

Information ArchitectureHigh level map of info requirements; blueprintCentralized:

data communications

Decentralized: focus on organizational function

Translates strategy into infrastructureHard to define: needs change

Information Infrastructure

Physical facilities, services, management supporting computing resources hardware Software networks & communications data personnel

Managerial Considerations

Existing ArchitectureCurrent & Future Requirements

Financial IssuesTechnical Issues

Evaluation Criteria: Applicability

Criteria Architecture Infrastructure

Strategic timeframe

Very Not

Technologicaladvances

Very Somewhat

Growthrequirements

Very Very

AssessingFinancial Issues

Somewhat Very

Evaluation Criteria: Applicability (cont)

Criteria (Technical)

Architecture Infrastructure

Standardization Very Very

Maintainability Very Very

Staff Experience Very Very

Meta Group Guidelines for Adaptable IT A&I

Plan modular (independent and loosely coupled) vs. monolithic

Have clear boundaries between infrastructure components

With network architecture, provide access to all users when it makes sense to do so

Architecture Definitions Mainframe- Computing environment in

which a large central computer handles all system functionality

Peer-to-peer- Architecture that allows networked computers to share resources without a central server playing a dominant role

Client/Server ArchitectureWireless (Mobile)- Computing environment

maintaining a data connection from a remote network using a wireless technology

Architecture Definitions - Client/serverClient - PC or workstation attached to a network

which is used to access shared network resourcesServer - machine that provides clients with

services (i.e., sharing databases, software)Thick client - full function stand-alone computer

that is used either exclusively or occasionally as a client in a client/server architecture

Thin client - computer hardware designed to be used only as a client in a client/server architecture (Network PCs)

Service Oriented Architecture (SOA)

SOA - architectural design pattern that concerns itself with defining loosely-coupled relationships between producers and consumers.

Guiding Principles Reuse, granularity, modularity, loosely

coupled, and interoperability Compliance to standards (both common and

industry-specific) Services identification and categorization,

provisioning and delivery, and monitoring and tracking

http://br.youtube.com/watch?v=sbd_1G8Kqjs

Before and After SOA

Top 10 Mistakes When Implementing SOA ZDNet News, 1/17/08, Callahan

Taking a shotgun approach (can’t afford indiscriminate use) Failing to involve business analysts (must consider business needs) Spending more time on SOA products than SOA planning Tackling the largest projects first (start with low-risk, smaller

projects) Forgetting that SOA is a business problem Treating identity as an afterthought Buying new products when exiting investments suffice (can usually

use existing hardware and software with SOA products) Misunderstanding company key players (know who ‘owns’ the

data) Expecting the SOA project to spread quickly (moving forward

incrementally and carefully ensures the most reuse) Lacking necessary elements (must have in-house resources or

expertise to implement) http://br.youtube.com/watch?v=0CbjUNzBV6I

Video – Vancouver International

Video Summary

Problem – Too Many NetworksVision – Superior AirportImplementation

Business Strategy – 2010 Olympics

Architecture – Wireless

Infrastructure – Cisco

Business Continuity PlanningApproved set of preparations and

sufficient procedures for responding to a variety of disaster events

Stages Pre-planning Planning Post-planning

Internal and external threats