1. Architecture & Infrastructure
Define: client/server, server, thick client, thin client, mainframe, legacy system, peer-to-peer
Distinguish architecture from infrastructure
Discuss the relationship between strategy, business requirements, architecture, and infrastructure
Discuss the applicability of evaluation criteria to architecture and infrastructure
Analyze infrastructure and architecture needs across hardware, software, data and networks
Describe the purpose and steps in Business Continuity Planning
Define and describe SOA 1

2. Who needs IT Architecture and Infrastructure?

3. Strategy, Requirements, Architecture & Infrastructure
Business Requirements
Architecture
Infrastructure

4. Information Architecture
High level map of info requirements; blueprint
Centralized:
data
communications
Decentralized:
focus on organizational function
Translates strategy into infrastructure
Hard to define: needs change 3

5. Information Infrastructure
Physical facilities, services, management supporting computing resources
hardware
Software
networks & communications
data
personnel 2

6. Managerial Considerations
Existing Architecture
Current & Future Requirements
Financial Issues
Technical Issues

7. Evaluation Criteria: Applicability

8. Evaluation Criteria: Applicability (cont)

9. 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

10. 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 Architecture
Wireless (Mobile)- Computing environment maintaining a data connection from a remote network using a wireless technology 5

11. Architecture Definitions - Client/server
Client - PC or workstation attached to a network which is used to access shared network resources
Server - 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) 5

12. 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, and interoperability
Compliance to standards (both common and industry-specific)
Services identification and categorization, provisioning and delivery, and monitoring and tracking

13. Video – Vancouver International

14. Video Summary Problem – Too Many Networks Vision – Superior Airport
Implementation
Business Strategy – 2010 Olympics
Architecture – Wireless
Infrastructure – Cisco

15. Business Continuity Planning
Approved set of preparations and sufficient procedures for responding to a variety of disaster events
Stages
Pre-planning
Planning
Post-planning
Internal and external threats 5