1 / 67

Review for Exam II

Review for Exam II. This exam will be administered Friday July 25, 2013, usual time and place. HW 10-4. HW S11-29. HWS11-30. Case Problem S11.1. HWS14-6. HW S14-24. Exam Format. 45-50 multiple choice 3 problems Closed-book Closed-notes Closed-neighbor

toni
Télécharger la présentation

Review for Exam II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Review for Exam II This exam will be administered Friday July 25, 2013, usual time and place

  2. HW 10-4

  3. HW S11-29

  4. HWS11-30

  5. Case Problem S11.1

  6. HWS14-6

  7. HW S14-24

  8. Exam Format • 45-50 multiple choice • 3 problems • Closed-book • Closed-notes • Closed-neighbor • BRING---pencil, calculator, orange scantron sheet

  9. Exam Coverage • Chapter 10, Chapter 11, Supplement to Ch 11, Supplement to Ch13, and Chapter 15-second half • LP problems in the supplement to Chapter 14, but not the content of Chapter 14—will cover that later.

  10. Typical problems—see Practice Exam II • Inventory with Independent Demand • Problems involving calculation of inventory turns and days of supply • Production Scheduling Problem • Transportation problem • LP formulation problem • Interpretation of LP SENSITIVITY output

  11. Typical Discussion Problems • Transshipment problem • Linear programming formulation • Be able to draw schematics of mainframe/glass architecture, client/server architecture and N-tier architecture

  12. Chapter 15 – ERP • Inventory for Dependent Demand will NOT be covered…. • Exam coverage of this chapter starts on page 700

  13. What were five motivations for transitioning from mainframes • Absence of data integration • 36 month backlogs at centralized MIS shops • Idle CPU cycles on desktops • Mainframes were expensive bottlenecks • Support for Internet and thin clients • Quicker, cheaper development times through REUSE

  14. What is the information architecture modern ERP systems are currently based on? Mainframe/glass house Client/server N-tier distributed None of these

  15. Every application software package consists of • Presentation management component • Business logic management component • Data management component • All of the above • 1 and 2 only

  16. ERP • Is software that organizes and manages a company’s business processes by sharing info across functional areas • Large caps have been there and done that—transitioned to ERP • Mid and small caps are getting there • The road to implementation has been rough

  17. More ERP • Based on an N-tier distributed architecture • Not on mainframe glasshouse

  18. Advantages of N-tier architecture • Provides for data integration • Better usage of MIPS on both PCs and servers • Solves the 36-month backlog of the centralized MIS shop • Enables a better career path for the MIS professional

  19. N-Tier distributed architecture • Is decentralized or centralized, or some combination of these (which?) • Utilizes thick clients or thin clients (which?)

  20. Sales & distribution Production & Materials Management Quality management Human resource management Project management Accounting and controlling/finance Supply chain management Customer relationship management ERP Modules

  21. ERP Terms • Best-of-breed • Collaborative product commerce • Customer relationship management • Supply chain management • XML

  22. Re-engineered Computer Architectures • Started with mainframe/glasshouse • Migrated to client/server • Evolved to N-tier distributed

  23. Why did such re-engineering occur? • There was no data integration • MIPs on mainframes were hugely expensive and very much in demand • MIPs on PCs were idle 95% of the time and extremely cheap • Backlogs for MIS shops were at 36 months • Developing new applications were slow and expensive

  24. Distributed architectures solved these problems • Data resides behind a single database engine

  25. Components of any Software Application Presentation Management Business Logic Data Management Database

  26. Components in brief PM BL DM

  27. Mainframe Architecture (circa 1993) Mainframe Computer PM PM PM BL BL BL DM DM DM

  28. Problems with Mainframe Architecture • Absence of data integration, resulting in little enterprise visibility • The applications are maintainable only by the centralized MIS shop, which is overloaded, resulting in 36 month lead times to get revisions effected • Every application had to be built from scratch, line-by-line, resulting in large cost and long lead times to create new applications

  29. More problems with Mainframe Architecture • No reuse was possible • These mainframe apps were accessed on networked PC’s via IBM 3278 terminal emulation software that was completely incompatible with the windows GUI applications—meaning no cut and paste • Mainframes were computational bottlenecks • Desktop PCs sat idle 99% of the time

  30. First solution: Client/server architecture Clients (PM, BL) Server (DM) Database

  31. These were known as thick clients • Because they contained both the presentation management (PM) and the business logic (BL) components of the application • Notice how the application is distributed across the network, residing in two computing boxes—the client or desktop and the server

  32. First solution: Client/server architecture Thick Clients (PM, BL) Server (DM) Database

  33. Advantages of Client/server architecture • All Data are all accessible behind the Server which runs the data management portion of the application—usually an Oracle Database engine • Now the marketing guy can see where his customer’s job is, and whether the customer is current with his payments, among other ‘things’

  34. Advantages of client/sever architecture • The IT professional could sit shoulder-to-shoulder with the end-user and develop applications as well as make changes to existing software rapidly, without a 36 month backlog • For new applications, there were huge reuse opportunities—in particular, the IT professional does not have to create a DM component—the Oracle engine can be reused

  35. Problems with Client/server • It wasn’t Internet compatible • It required an IT professional to install software on the end-user’s personal computer (the client) • It required an IT professional to work closely with the non-IT professional • There were no career paths for IT professional hired in marketing, finance, accounting, manufacturing, etc.

  36. Modern solution of today: N-TIER DISTRIBUTED ARCHITECTURE • This is a distributed architecture like client/server, but now the application is distributed across three or more computing boxes on the network

  37. N-Tier distributed Architecture Thin Clients (1/2PM) Data Server (DM) Database Application Server 1 Application Server 2

  38. Take a closer look at the Application Servers Application Server runs the business logic component and half ot the presentation management component—the portion the serves out the web pages

  39. Comments on N-Tier Distributed Architecture • Clients are called ‘thin’ because the only thing running on them is the Internet Browser • The IT professional doesn’t have to install anything on the client • More re-use is possible—specifically that browser

  40. Advantages of N-Tier Distributed Architecture • Like Client/server, it accommodates enterprise visibility because the data are integrated • Applications can be built rapidly because there is abundant reuse • The DM module is reused • Half of the PM component is reused • There are reuse opportunities within the rest of the PM component and the BL component as well

  41. More advantages of N-Tier • IT professionals don’t have to be remotely loaned out to marketing, management, accounting and finance • They can now be centrally located and managed where career paths will exist for them

  42. Application Servers do Two things • They serve out web pages upon request • They do all of the business logic processing.

  43. ERP Modules • Finance/Accounting • Sales Marketing • Production/Materials Management • Human Resources • Supply Chain Management • Customer Relation Management

  44. These modules would be placed in a • Thin client • Data server • Application server • Mainframe WHICH??

  45. ERP Implementation • Analyze business processes • Choose modules to implement • Align level of sophistication • Finalize delivery and access • Link with External Partners

  46. Customer Relationship Management • CRM software plans and executes business processes that involve customer interaction, such as marketing, sales, fulfillment, and service (not manufacturing) • CRM is focused on customers, not products

  47. Collaborative Product Commerce • Software concerned with new product design and development, as well as product lifecycle management

  48. Connectivity • A common data management component • API’s (Application Programming Interfaces) • EAI (Enterprise Application Integration) • XML (Extensible Markup Language) • Dr. Viator (accounting) teaches a course in this language

  49. Chapter 10--Supply Chain Management • Plants/warehouses/distribution/ information infrastructure • Most of America’s product gets moved by _____ (air, water, rail, truck, pipeline). • What is COVISINT?? • What benefits accrue from SCM?

  50. What’s new and exciting in SCM?? • Information Technology (specifically enterprise visibility) • Has changed everything • SCM Software modules within ERP systems • I2 Technologies • Has reduced uncertainty • Which has reduced _____________ • Which is a form of _______________

More Related