CHAPTER 5 ENTERPRISE ARCHITECTURES

1. Business Driven Information Systems 2e CHAPTER 5 ENTERPRISE ARCHITECTURES

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

3. SECTION 5.1 MANAGING ENTERPRISE ARCHITECTURES

4. LEARNINGOUTCOMES 5.1 Explain the three components of an enterprise architecture 5.2 Describe how an organization can implement a solid information architecture

5. LEARNINGOUTCOMES 5.3 List and describe the five-ilities in an infrastructure architecture 5.4 Compare web services and open systems

6. 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 in technology, fluent in business, a patient diplomat, and provides the important bridge between IT and the business

7. ENTERPRISE ARCHITECTURES • Primary goals of enterprise architectures

8. ENTERPRISE ARCHITECTURES

9. INFORMATION ARCHITECTURE • Information architecture - identifies where and how important information, such as customer records, is maintained and secured • Enterprise information architecture should focus on: • Backup and recovery • Disaster recovery • Information security

10. INFORMATION ARCHITECTURE

11. Backup and Recovery • Backup -an exact copy of a system’s information • Recovery - the ability to get a system up and running in the event of a system crash or failure and includes restoring the information backup

12. Backup and Recovery • Fault tolerance -a computer system designed that in the event a component fails, a backup component or procedure can immediately take its place with no loss of service • Failover - a backup operational mode in which the functions of a computer component (such as a processor, server, network, or database) is assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time

13. Disaster Recovery • Disaster recovery best practices include: • Mind the enterprise architectures • Monitor the quality of computer networks that provide data on power suppliers and demand • Make sure the networks can be restored quickly in the case of downtime • Set up disaster recovery plans • Provide adequate staff training

14. Disaster Recovery • Financial Institutions Worldwide Spending on Disaster Recovery

15. Disaster Recovery • Disaster recovery plan -a detailed process for recovering information or an IT system in the event of a catastrophic disaster such as a fire or flood • Disaster recovery cost curve - charts (1) the cost to the organization of the unavailability of information and technology and (2) the cost to the organization of recovering from a disaster over time

16. Disaster Recovery

17. Disaster Recovery • Hot site - a separate and fully equipped facility where the company can move immediately after a disaster and resume business • Cold site - a separate facility that does not have any computer equipment, but is a place where employees can move after a disaster

18. Disaster Recovery • Business continuity planning (BCP) - is a plan for how an organization will recover and restore partially or completely interrupted critical function(s) within a predetermined time after a disaster or extended disruption

19. Information Security • Good information architectures include… • A strong information security plan • Managing user access • Up-to-date antivirus software and patches

20. INFRASTRUCTURE ARCHITECTURE • Infrastructure architecture - includes the hardware, software, and telecommunicationsequipment that, when combined, provides the underlying foundation to support the organization’s goals • As an organization changes, its systems must be able to change to support its operations

21. INFRASTRUCTURE ARCHITECTURE

22. INFRASTRUCTURE ARCHITECTURE • Five primary characteristics of a solid infrastructure architecture: • Flexibility • Scalability • Reliability • Availability • Performance

23. Flexibility • Organizations must watch today’s business, as well as tomorrow’s, when designing and building systems • Systems must be flexible enough to meet all types of business changes

24. Scalability • Scalability - refers to how well a system can adapt to increased demands • Capacity planning - determines the future IT infrastructure requirements for new equipment and additional network capacity • Performing a capacity plan is one way to ensure the IT infrastructure is scalable

25. Reliability • Reliability ensures all systems are functioning correctly and providing accurate information • Reliability is another term for accuracy when discussing the correctness of systems within the context of efficiency IT metrics

26. Availability • Availability - addresses when systems can be accessed by users • High availability - refers to a system or component that is continuously operational for a desirably long length of time

27. Performance • Performance - measures how quickly a system performs a certain process or transaction (in terms of efficiency IT metrics of both speed and throughput) • Not having enough performance capacity can have a devastating, negative impact on a business

28. APPLICATION ARCHITECTURE • Application architecture - determines how applications integrate and relate to each other • With new architectures, IT can build new business capabilities faster, cheaper, and in a vocabulary the business can understand

29. Web Services • Web service -contains a repertoire of Web-based data and procedural resources that use shared protocols 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 different manufacturers

30. Web Services

31. Web Services • The two primary parts of web services are: • Event -detect threats and opportunities and alert those who can act on the information • Service - more like software products than they are coding projects • Need to be reusable if they are going to have an impact on productivity

32. Open Systems • Open system -a broad, general term that describes nonproprietary IT hardware and software made available by the standards and procedures by which their products work, making it easier to integrate them • Open source -refers to any program whose source code is made available for use or modification as users or other developers see fit

33. OPENING CASE QUESTIONSVirgin Mobile • How can an organization use an information architecture to protect its IT investment in electronic devices outlined in the case? • How can an organization use the architectures mentioned in the case to protect information security? • Identify the five-ilites and rank them in order of importance for a cell phone (1 highest, 5 lowest) • Describe the importance of web services and open systems to companies such as Virgin Mobile

34. SECTION 5.2 ARCHITECTURE TRENDS

35. LEARNING OUTCOMES 5.5 Describe the business value in deploying a service oriented architecture 5.6 Explain the need for interoperability and loose coupling in building today’s IT systems

36. LEARNING OUTCOMES 5.7 Identify the logical functions used in a virtualized environment 5.8 Explain the business benefits of grid computing

37. ARCHITECTURE TRENDS • Organizations today must continually watch new architecture trends to ensure they can keep up with new and disruptive technologies • Three architecture trends that are quickly becoming requirements for all businesses including: • Service oriented architecture • Virtualization • Grid computing

38. SERVICE ORIENTED ARCHITECTURE • Service oriented architecture(SOA) is a business-driven IT architectural approach that supports integrating a business as linked, repeatable tasks or services • SOA ensures IT systems can adapt quickly, easily, and economically to support rapidly changing business needs

39. SERVICE ORIENTED ARCHITECTURE

40. SOA Business Benefits • The key technical concepts of SOA are: • Services • Interoperability • Loose coupling

41. SOA Business Benefits

42. Service • Service oriented architecture begins with a service • (A SOA) service - can be a business task, such as checking a potential customer's credit rating only opening a new account • Services are “like” software products

43. Service

44. Interoperability • Interoperability - is the capability of two or more computer systems to share data and resources, even though they are made by different manufacturers • Extensible Markup Language (XML) - amarkup language for documents containing structured information

45. Loose Coupling • Loose coupling - is the capability of services to be joined together on demand to create composite services, 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

46. VIRTUALIZATION • Virtualization - is a framework of dividing the resources of a computer into multiple execution environments • It is a way of increasing physical resources to maximize the investment in hardware

47. VIRTUALIZATION

48. What are Virtual Machines? • System virtualization - is the ability to present the resources of a single computer as if it is a collection of separate computers ("virtual machines") • Each with its own virtual CPUs, network interfaces, storage, and operating system

49. What are Virtual Machines?

50. Virtualization Business Benefits • Trends that have moved virtualization into the spotlight: • Hardware being underutilized • Data centers running out of space • Increased energy costs • System administration costs mounting