Lecture 5 Wk 05

Embed Size (px)

Citation preview

  • 7/31/2019 Lecture 5 Wk 05

    1/58

    Topic Three : Essentials of InformationSystems

  • 7/31/2019 Lecture 5 Wk 05

    2/58

    Learning Outcome The student shall be able to evaluate markets for IT

    products, major vendors, factors affecting major IT-related decisions

    Ethics in Information Technology, Fourth Edition 2

  • 7/31/2019 Lecture 5 Wk 05

    3/58

    Performance Criteria:

    3.1 Evaluate enterprise architecture

    3.2 Evaluate the Data and Data Warehousesapplications

    3.3 Evaluate the Networks in Information Systemsenvironment

    3.4 Evaluate Telecommunications and mobiletechnologies in Information Systems

    Ethics in Information Technology, Fourth Edition 3

  • 7/31/2019 Lecture 5 Wk 05

    4/58

    Chapter 5:Enterprise Architecture

    4

  • 7/31/2019 Lecture 5 Wk 05

    5/58

    CHAPTER FIVE OVERVIEW SECTION 5.1 - MANAGING ENTERPRISE

    ARCHITECTURES Enterprise Architectures

    Information Architecture

    Infrastructure Architecture

    Application Architecture

    SECTION 5.2 - ARCHITECTURE TRENDS Service Oriented Architecture

    Virtualization

    Grid Computing

    5-2

  • 7/31/2019 Lecture 5 Wk 05

    6/58

    MANAGING ENTERPRISE

    ARCHITECTURES

    Section 5.1

    4-4

  • 7/31/2019 Lecture 5 Wk 05

    7/58

    LEARNING OUTCOMES5.1 Explain the three components of an

    enterprise architecture

    5.2 Describe how an organization can

    implement a solid informationarchitecture

    5-4

  • 7/31/2019 Lecture 5 Wk 05

    8/58

    LEARNING OUTCOMES5.3 List and describe the five-ilities in an

    infrastructure architecture

    5.4 Compare web services and open

    systems

    5-5

  • 7/31/2019 Lecture 5 Wk 05

    9/58

    ENTERPRISE ARCHITECTURES Enterprise architecture - includes the plans for

    how an organization will build, deploy, use, and

    share its data, processes, and IT assets

    Enterprise architect (EA) -a person grounded intechnology, fluent in business, a patient diplomat,

    and provides the important bridge between IT andthe business

    5-6

  • 7/31/2019 Lecture 5 Wk 05

    10/58

    ENTERPRISE ARCHITECTURES Primary goals of enterprise architectures

    5-7

  • 7/31/2019 Lecture 5 Wk 05

    11/58

    ENTERPRISE ARCHITECTURES

    5-8

  • 7/31/2019 Lecture 5 Wk 05

    12/58

    INFORMATION ARCHITECTURE Information architecture - identifies where and how

    important information, such as customer records, ismaintained and secured

    Enterprise information architecture should focus on:

    1. Backup and recovery

    2. Disaster recovery3. Information security

    5-9

  • 7/31/2019 Lecture 5 Wk 05

    13/58

    INFORMATION ARCHITECTURE

    5-10

  • 7/31/2019 Lecture 5 Wk 05

    14/58

    BACKUP AND RECOVERY Backup -an exact copy of a systems information

    Recovery

    -the ability to get a system up and running in

    the event of a system crash or failure and includesrestoring the information backup

    5-11

  • 7/31/2019 Lecture 5 Wk 05

    15/58

    BACKUP AND RECOVERY Fault tolerance -a computer system designed that in

    the event a component fails, a backup component orprocedure can immediately take its place with no loss

    of service

    Failover- a backup operational mode in which thefunctions of a computer component (such as a

    processor, server, network, or database) is assumed bysecondary system components when the primarycomponent becomes unavailable through either failureor scheduled down time

    5-12

  • 7/31/2019 Lecture 5 Wk 05

    16/58

    DISASTER RECOVERYDisaster recovery best practices

    include:

    Mind the enterprise architecturesMonitor the quality of computer networksthat provide data on power suppliers anddemand

    Make sure the networks can be restoredquickly in the case of downtimeSet up disaster recovery plansProvide adequate staff training

    5-13

  • 7/31/2019 Lecture 5 Wk 05

    17/58

    DISASTER RECOVERY Financial Institutions Worldwide Spending on Disaster

    Recovery

    5-14

  • 7/31/2019 Lecture 5 Wk 05

    18/58

    DISASTER RECOVERY Disaster recovery plan -a detailed process for

    recovering information or an IT system in the event ofa catastrophic disaster such as a fire or flood

    Disaster recovery cost curve - charts (1) the cost tothe organization of the unavailability of informationand technology and (2) the cost to the organization ofrecovering from a disaster over time

    5-15

  • 7/31/2019 Lecture 5 Wk 05

    19/58

    DISASTER RECOVERY

    5-16

  • 7/31/2019 Lecture 5 Wk 05

    20/58

    DISASTER RECOVERY Hot site - a separate and fully equipped facility where

    the company can move immediately after a disasterand resume business

    Cold site - a separate facility that does not have anycomputer equipment, but is a place where employees

    can move after a disaster

    5-17

  • 7/31/2019 Lecture 5 Wk 05

    21/58

    DISASTER RECOVERY Business continuity planning (BCP) - is a plan for

    how an organization will recover and restore partiallyor completely interrupted critical function(s) within apredetermined time after a disaster or extendeddisruption

    5-18

  • 7/31/2019 Lecture 5 Wk 05

    22/58

    INFORMATION SECURITY

    Good information architectures include A strong information security plan

    Managing user access Up-to-date antivirus software and patches

    5-19

  • 7/31/2019 Lecture 5 Wk 05

    23/58

    INFRASTRUCTURE ARCHITECTURE Infrastructure architecture - includes the hardware,

    software, and telecommunicationsequipment that,when combined, provides the underlying foundationto support the organizations goals

    As an organization changes, its systems must be able

    to change to support its operations

    5-20

  • 7/31/2019 Lecture 5 Wk 05

    24/58

    INFRASTRUCTURE ARCHITECTURE

    5-21

  • 7/31/2019 Lecture 5 Wk 05

    25/58

    INFRASTRUCTURE ARCHITECTURE Five primary characteristics of a solid

    infrastructure architecture:

    1. Flexibility

    2. Scalability

    3. Reliability

    4. Availability

    5. Performance

    5-22

  • 7/31/2019 Lecture 5 Wk 05

    26/58

    FLEXIBILITY Organizations must watch todays business, as well as

    tomorrows, when designing and building systems

    Systems must be flexible enough to meet all types ofbusiness changes

    5-23

  • 7/31/2019 Lecture 5 Wk 05

    27/58

    SCALABILITY Scalability - refers to how well a system can adapt to

    increased demands

    Capacity planning - determines the future ITinfrastructure requirements for new equipment andadditional network capacity

    Performing a capacity plan is one way to ensure the ITinfrastructure is scalable

    5-24

  • 7/31/2019 Lecture 5 Wk 05

    28/58

    RELIABILITY Reliability ensures all systems are functioning

    correctly and providing accurate information

    Reliability is another term for accuracy whendiscussing the correctness of systems within thecontext of efficiency IT metrics

    5-25

  • 7/31/2019 Lecture 5 Wk 05

    29/58

    AVAILABILITY Availability - addresses when systems can be accessed

    by users

    High availability - refers to a system or componentthat is continuously operational for a desirably longlength of time

    5-26

  • 7/31/2019 Lecture 5 Wk 05

    30/58

    PERFORMANCE Performance - measures how quickly a system

    performs a certain process or transaction (in terms ofefficiency IT metrics of both speed and throughput)

    Not having enough performance capacity can have adevastating, negative impact on a business

    5-27

  • 7/31/2019 Lecture 5 Wk 05

    31/58

    APPLICATION ARCHITECTURE Application architecture - determines how

    applications integrate and relate to each other

    With new architectures, IT can build new businesscapabilities faster, cheaper, and in a vocabulary thebusiness can understand

    5-28

  • 7/31/2019 Lecture 5 Wk 05

    32/58

    WEB SERVICES Web service -contains a repertoire of Web-based

    data and procedural resources that use sharedprotocols and standards permitting different

    applications to share data and services

    Interoperability - the capability of two or more

    computer systems to share data and resources,even though they are made by differentmanufacturers

    5-29

  • 7/31/2019 Lecture 5 Wk 05

    33/58

    WEB SERVICES

    5-30

  • 7/31/2019 Lecture 5 Wk 05

    34/58

    WEB SERVICES The two primary parts of web services are:

    1. Event -detect threats and opportunities and alertthose who can act on the information

    2. Service - more like software products than they arecoding projects Need to be reusable if they are going to have an impact on

    productivity

    5-31

  • 7/31/2019 Lecture 5 Wk 05

    35/58

    OPEN SYSTEMS Open system -a broad, general term that describes

    nonproprietary IT hardware and software madeavailable by the standards and procedures by which

    their products work, making it easier to integrate them

    Open source -refers to any program whose sourcecode is made available for use or modification as users

    or other developers see fit

    5-32

  • 7/31/2019 Lecture 5 Wk 05

    36/58

    ARCHITECTURE TRENDS

    Section 5.2

    4-4

  • 7/31/2019 Lecture 5 Wk 05

    37/58

    LEARNING OUTCOMES5.5 Describe the business value in

    deploying a service oriented

    architecture

    5.6 Explain the need for interoperabilityand loose coupling in buildingtodays IT systems

    5-34

  • 7/31/2019 Lecture 5 Wk 05

    38/58

    LEARNING OUTCOMES5.7 Identify the logical functions used in

    a virtualized environment

    5.8 Explain the business benefits of grid

    computing

    5-35

  • 7/31/2019 Lecture 5 Wk 05

    39/58

    ARCHITECTURE TRENDS Organizations today must continually watch new

    architecture trends to ensure they can keep up withnew and disruptive technologies

    Three architecture trends that are quickly becomingrequirements for all businesses including:

    1. Service oriented architecture2. Virtualization

    3. Grid computing

    5-36

  • 7/31/2019 Lecture 5 Wk 05

    40/58

    SERVICE ORIENTED ARCHITECTURE Service oriented architecture(SOA) is a business-

    driven IT architectural approach that supportsintegrating a business as linked, repeatable tasks or

    services

    SOA ensures IT systems can adapt quickly, easily, and

    economically to support rapidly changing businessneeds

    5-37

  • 7/31/2019 Lecture 5 Wk 05

    41/58

    SERVICE ORIENTED ARCHITECTURE

    5-38

  • 7/31/2019 Lecture 5 Wk 05

    42/58

    SOA BUSINESS BENEFITSThe key technical concepts of SOA are:

    Services

    Interoperability

    Loose coupling

    5-39

  • 7/31/2019 Lecture 5 Wk 05

    43/58

    SOA BUSINESS BENEFITS

    5-40

  • 7/31/2019 Lecture 5 Wk 05

    44/58

    SERVICEService oriented architecture begins with a

    service

    (A SOA) service - can be a business task,such as checking a potential customer'scredit rating only opening a new account

    Services are like software products

    5-41

  • 7/31/2019 Lecture 5 Wk 05

    45/58

    SERVICE

    5-42

  • 7/31/2019 Lecture 5 Wk 05

    46/58

    INTEROPERABILITYInteroperability - is the capability of

    two or more computer systems to share

    data and resources, even though theyare made by different manufacturers

    Extensible Markup Language (XML)- amarkup language for documentscontaining structured information

    5-43

  • 7/31/2019 Lecture 5 Wk 05

    47/58

    LOOSE COUPLING Loose coupling - is the capability of services to be

    joined together on demand to create compositeservices, or disassembled just as easily into their

    functional components

    Loose coupling is a way of ensuring that the technical

    details are decoupled from the service

    5-44

  • 7/31/2019 Lecture 5 Wk 05

    48/58

    VIRTUALIZATIONVirtualization - is a framework of

    dividing the resources of a computer

    into multiple execution environments

    It is a way of increasing physicalresources to maximize the investmentin hardware

    5-45

  • 7/31/2019 Lecture 5 Wk 05

    49/58

    VIRTUALIZATION

    5-46

  • 7/31/2019 Lecture 5 Wk 05

    50/58

    WHAT ARE VIRTUAL MACHINES? System virtualization - is the ability to present the

    resources of a single computer as if it is a collection ofseparate computers ("virtual machines")

    Each with its own virtual CPUs, network interfaces,storage, and operating system

    5-47

  • 7/31/2019 Lecture 5 Wk 05

    51/58

    WHAT ARE VIRTUAL MACHINES?

    5-48

  • 7/31/2019 Lecture 5 Wk 05

    52/58

    VIRTUALIZATION BUSINESS

    BENEFITSTrends that have moved virtualization

    into the spotlight:

    Hardware being underutilized

    Data centers running out of space

    Increased energy costs

    System administration costs mounting

    5-49

  • 7/31/2019 Lecture 5 Wk 05

    53/58

    ADDITIONAL VIRTUALIZATION

    BENEFITSRapid application deployment

    Dynamic load balancing

    Streamlined disaster recovery

    5-50

  • 7/31/2019 Lecture 5 Wk 05

    54/58

    GRID COMPUTING Grid computing - is an aggregation of geographically

    dispersed computing, storage, and network resources,coordinated to deliver improved performance, higher

    quality of service, better utilization, and easier accessto data

    5-51

  • 7/31/2019 Lecture 5 Wk 05

    55/58

    GRID COMPUTING

    5-52

  • 7/31/2019 Lecture 5 Wk 05

    56/58

    GRID COMPUTING BUSINESS BENEFITS Improving productivity and collaboration of virtual

    organizations and respective computing and dataresources

    Allowing widely dispersed departments andbusinesses to create virtual organizations to share dataand resources

    Building robust and infinitely flexible and resilientoperational architectures

    5-53

  • 7/31/2019 Lecture 5 Wk 05

    57/58

    GRID COMPUTING BUSINESS

    BENEFIT Providing instantaneous access to massive computing

    and data resources

    Leveraging existing capital investments, which in turnhelp to ensure optimal utilization and costs ofcomputing capabilities

    5-54

  • 7/31/2019 Lecture 5 Wk 05

    58/58

    GRID COMPUTING BUSINESS

    BENEFITS