ISM3003- Exam 3 Study GuideChapter 7- Enterprise Infrastructure, Metrics, and Business Continuity Planning1. SoAa. Service oriented architecture (SoA)- perspective that focuses on the development, use, and reuse of small self-contained blocks of code to meet all application software needsb. Software code is not developed solely for a single application, instead services are built that can be used and reused across all applicationsc. An SoA Organization would be: 1. Lean and agile using resources in the best way2. Proactive in addressing changes in the market3. Quick to respond and adapt to advances in tech4. Transformational in its processes, structure and HR initiatives to match a changing and dynamic workforced. SoA focused Specifically on IT:1. Customers2. End Users3. Software development4. Information needs5. Hardware requirements e. Customers 1. Customers should be able to “plug and play” into your organization and have the same pleasurable experience regardless of the channel2. Multi-channel service delivery3. Consistent, high-quality interactions regardless of the venue4. Customizable product and service capabilitiesf. End Users1. End Users should have access to whatever information and software they need regardless of where they are2. Fully integrated ERP system3. Interoperability among vendors4. Interoperability of modules by the same vendor5. Mobile computingg. Software Development1. Software development should focus on reusable components to accelerate systems development. This means using component-based development methodologies and taking advantage of exciting Web 2.0 applications.2. SoA as a framework3. RAD, XP, and agile as development methodologies 4. Exciting new deployments like Web 2.0h. Information Needs1. Information would be treated appropriately as a valuable organizational resource- protected, managed, organized, and made available to everyone who needs it.2. End users with access to all types of information3. Integrated information, business intelligence, and knowledge4. Data warehouses5. Standard information formats6. Integrity controls7. No duplicate informationi. Hardware Requirements1. Hardware is both integrated and transparent 2. Integration of different technologies and tech platforms3. Large storage capacity4. Your focus on logical, not physical5. Safe and secure telecommunications platform2. Hardware and Software Infrastructurea. Infrastructure- the structure beneath a structure1. IT infrastructure is the implementation of your organizations architectureb. ERP Revisited1. Enterprise resource planning (ERP) system- collection of integrated software for business management, accounting finance, etc…2. ERP is big business3. Dominant ERP providers- SAP, Oracle, SSA Global, Microsoftc. ERP Evolution1. MRP- 1970s, focus on production planning, calculating time requirements, procurement, basic automated manufacturing focus2. MRP II- 1980s, closed the loop to include financial and accounting systems andserve as a decision support tool for managers3. ERP- late 1980s/early 1990s, focus on critical “time to market”, shorter lead times, customers want it now4. ERP II- today, focus on complete ERP integration with CRM, business intelligence, and a host of other applications across the organization d. ERP and SoA1. For ERP to integrate everything, it must be plug-and-play components or services2. All modules of an ERP vendor must be interoperable3. Software from multiple ERP vendors must be interoperable 4. The infrastructure beneath must be hidden from users and customerse. SoA-Enabled ERP Advantages1. Reliable information access 2. Avoids data and operations redundancy 3. Delivery and cycle time reduction4. Cost reduction5. Easy adaptability6. Improved scalability7. Global outreach8. E-business supportf. SoA-Enabled ERP Disadvantages1. Time-consuming2. Expensive3. Lack of conformity of modules4. Vendor dependence5. Too many features7. Too complex8. Questionable scalability 9. Not enough extended ERP capability3. Supporting Network Infrastructuresa. Computer network- fundamental underlying infrastructure for any IT environment:b. Decentralized Network Infrastructure- involves little or no sharing of IT and other resources such as information1. Almost nonexistent todayc. Centralized- sharing information systems in one central area or on one central mainframe1. Like decentralized, almost nonexistent todayd. Distributed- distributing the information and processing power of IT systems via a network1. First true network infrastructure2. Processing activity is allocated to the locations where it can most efficiently bedonee. Client/server infrastructure (network)- one or more computers that are servers which provide services to other computers, called clients1. Servers and clients work together to optimize processing, info storage, etc…2. When you surf the Web, the underlying network infrastructure is client/serverf. Tiered (layer)- the IT system is partitioned into tiers where each tier performs a specific type of functionality 1. 1-Tier- single machine2. 2-Tier- basic client/server relationship3. 3-Tier- client, application server, data or database server4. N-Tier- scalable 3-tier structure with more servers4. IT Success Metricsa. To justify costs of technology, you need to measure its successb. Metrics are also called benchmarks, baseline values a system seeks to attainc. Benchmarking- process of continuously measuring system result and comparing themto benchmarks5. Efficiency & Effectiveness Metricsa. Efficiency- doing something right1. In the least time2. At the lowest cost3. With the fewest errorsb. Effectiveness- doing the right things1. Getting customers to buy when they visit your site2. Answering the right question with the right answer the first timec. Bottom-line initiatives typically focus on efficiency, while top-line initiatives tend to focus on effectiveness 6. Types of IT Success Metricsa. Infrastructure-Centric Metric- measure of efficiency, speed and/or capacity of tech1. Throughput- amount of information that can pass through a system is a given amount of time2. Transaction speed- speed at which a system can process a transaction3. System availability- measured inversely as downtime, or the average amount of time a system is down or unavailable 4. Accuracy- measured inversely as error rate, or the number of errors per thousand/million that a system generates5. Response time- average time to respond to a user-generated event,