MEIE881 Architecture and Infrastructure Architecture ...


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 1
  • 3
  • 2
  • 5
  • 5
  • 5
  • MEIE881 Architecture and Infrastructure Architecture ...

    1. 1. MEIE881 Architecture and Infrastructure
    2. 2. Architecture & Infrastructure <ul><li>Define: client/server, server, thick client, thin client, mainframe, legacy system, peer-to-peer </li></ul><ul><li>Distinguish architecture from infrastructure </li></ul><ul><li>Discuss the relationship between strategy, business requirements, architecture, and infrastructure </li></ul><ul><li>Discuss the applicability of evaluation criteria to architecture and infrastructure </li></ul><ul><li>Analyze infrastructure and architecture needs across hardware, software, data and networks </li></ul><ul><li>Describe the purpose and steps in Business Continuity Planning </li></ul><ul><li>Define and describe SOA </li></ul>
    3. 3. Who needs IT Architecture and Infrastructure?
    4. 4. Strategy, Requirements, Architecture & Infrastructure <ul><li>Strategy </li></ul><ul><li>Business Requirements </li></ul><ul><li>Architecture </li></ul><ul><li>Infrastructure </li></ul>
    5. 5. Information Architecture <ul><li>High level map of info requirements; blueprint </li></ul><ul><li>Centralized: </li></ul><ul><ul><li>data </li></ul></ul><ul><ul><li>communications </li></ul></ul><ul><li>Decentralized: </li></ul><ul><ul><li>focus on organizational function </li></ul></ul><ul><li>Translates strategy into infrastructure </li></ul><ul><li>Hard to define: needs change </li></ul>
    6. 6. Information Infrastructure <ul><li>Physical facilities, services, management supporting computing resources </li></ul><ul><ul><li>hardware </li></ul></ul><ul><ul><li>Software </li></ul></ul><ul><ul><li>networks & communications </li></ul></ul><ul><ul><li>data </li></ul></ul><ul><ul><li>personnel </li></ul></ul>
    7. 7. Managerial Considerations <ul><li>Existing Architecture </li></ul><ul><li>Current & Future Requirements </li></ul><ul><li>Financial Issues </li></ul><ul><li>Technical Issues </li></ul>
    8. 8. Evaluation Criteria: Applicability
    9. 9. Evaluation Criteria: Applicability (cont)
    10. 10. Meta Group Guidelines for Adaptable IT A&I <ul><li>Plan modular (independent and loosely coupled) vs. monolithic </li></ul><ul><li>Have clear boundaries between infrastructure components </li></ul><ul><li>With network architecture, provide access to all users when it makes sense to do so </li></ul>
    11. 11. Architecture Definitions <ul><li>Mainframe- Computing environment in which a large central computer handles all system functionality </li></ul><ul><li>Peer-to-peer- Architecture that allows networked computers to share resources without a central server playing a dominant role </li></ul><ul><li>Client/Server Architecture </li></ul><ul><li>Wireless (Mobile)- Computing environment maintaining a data connection from a remote network using a wireless technology </li></ul>
    12. 12. Architecture Definitions - Client/server <ul><li>Client - PC or workstation attached to a network which is used to access shared network resources </li></ul><ul><li>Server - machine that provides clients with services (i.e., sharing databases, software) </li></ul><ul><li>Thick client - full function stand-alone computer that is used either exclusively or occasionally as a client in a client/server architecture </li></ul><ul><li>Thin client - computer hardware designed to be used only as a client in a client/server architecture (Network PCs) </li></ul>
    13. 13. Service Oriented Architecture (SOA) <ul><li>SOA - architectural design pattern that concerns itself with defining loosely-coupled relationships between producers and consumers. </li></ul><ul><li>Guiding Principles </li></ul><ul><ul><li>Reuse, granularity, modularity, loosely coupled, and interoperability </li></ul></ul><ul><ul><li>Compliance to standards (both common and industry-specific) </li></ul></ul><ul><ul><li>Services identification and categorization, provisioning and delivery, and monitoring and tracking </li></ul></ul><ul><ul><li> </li></ul></ul>
    14. 14. Before and After SOA
    15. 15. Top 10 Mistakes When Implementing SOA ZDNet News, 1/17/08, Callahan <ul><li>Taking a shotgun approach (can’t afford indiscriminate use) </li></ul><ul><li>Failing to involve business analysts (must consider business needs) </li></ul><ul><li>Spending more time on SOA products than SOA planning </li></ul><ul><li>Tackling the largest projects first (start with low-risk, smaller projects) </li></ul><ul><li>Forgetting that SOA is a business problem </li></ul><ul><li>Treating identity as an afterthought </li></ul><ul><li>Buying new products when exiting investments suffice (can usually use existing hardware and software with SOA products) </li></ul><ul><li>Misunderstanding company key players (know who ‘owns’ the data) </li></ul><ul><li>Expecting the SOA project to spread quickly (moving forward incrementally and carefully ensures the most reuse) </li></ul><ul><li>Lacking necessary elements (must have in-house resources or expertise to implement) </li></ul><ul><li> </li></ul>
    16. 16. Video – Vancouver International
    17. 17. Video Summary <ul><li>Problem – Too Many Networks </li></ul><ul><li>Vision – Superior Airport </li></ul><ul><li>Implementation </li></ul><ul><ul><li>Business Strategy – 2010 Olympics </li></ul></ul><ul><ul><li>Architecture – Wireless </li></ul></ul><ul><ul><li>Infrastructure – Cisco </li></ul></ul>
    18. 18. Business Continuity Planning <ul><li>Approved set of preparations and sufficient procedures for responding to a variety of disaster events </li></ul><ul><li>Stages </li></ul><ul><ul><li>Pre-planning </li></ul></ul><ul><ul><li>Planning </li></ul></ul><ul><ul><li>Post-planning </li></ul></ul><ul><li>Internal and external threats </li></ul>