MIS 17 Cross-Functional Enterprise Systems


Published on

These presentations are created by Tushar B Kute to teach the subject 'Management Information System' subject of TEIT of University of Pune.

Published in: Education
  • Be the first to comment

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

No notes for slide

MIS 17 Cross-Functional Enterprise Systems

  1. 1. Management information system<br />Third Year Information Technology<br />Part 17<br />Cross-Functional Enterprise Systems<br />Tushar B Kute,<br />Sandip Institute of Technology & <br />Research Centre, Nashik<br />tbkute@gmail.com<br />
  2. 2. E-commerce vs. e-business<br />
  3. 3. Cross-functional enterprise system<br />It is a group of people with different functional expertise working towards a common goal.<br />It may include the people from finance, marketing, operations, human resources. Typically, it includes employees from all levels of an organization.<br />Cross-functional enterprise system often function as self-directed enterprise systems responding to broad, but not specific directives.<br />
  4. 4. evolution<br />Task Orientation<br />Functional Orientation<br />Cross-functional system <br />
  5. 5. Application frameworks<br />Customer Relationship Management<br />Supply Chain Management<br />Selling Chain Management<br />Enterprise Resource Management<br />Enterprise Application Integration<br />E-procurement<br />Knowledge Management<br />Decision Support<br />Business Intelligence<br />
  6. 6. Cross-functional system architecture<br />Supplier<br />Business Partners<br />SCM<br />Employees<br />ERP<br />Partner Relationship <br />Management<br />Knowledge <br />Management<br />EAI<br />CRM<br />SeCM<br />Customer<br />
  7. 7. Collaboration system in manufacturing<br />It is designed for one basic purpose, to help unite employees or people that are working on similar task, or it could be the exact task and system helps unite them to complete their task and achieve whatever goal that task sets out to do.<br />E.g. Slovak, Instant Messaging<br />
  8. 8. Enterprise collaboration system<br />Communicate<br />Coordinate<br />Collaborate and Cooperation<br />
  9. 9. Tools used<br />Electronic mail<br />Voice mail<br />Bulletin board systems<br />Fax<br />Video conferencing tools<br />
  10. 10. Collaboration system in manufacturing<br />Structured collaboration system<br />Easier to organize<br />Excellent for hierarchical organizations<br />Increases proficiency<br />Limitations of structured collaboration system<br />Same workflow information<br />Can cause groupthink<br />Encourages lack of creativity<br />
  11. 11. Enterprise application integration<br />The use of software and computer systems architectural principles to integrate a set of enterprise computer applications.<br />It is an integration framework composed of collection of technologies and services which form a middleware to enable integration of systems and applications across the enterprise. <br />
  12. 12. Transaction processing systems <br />A transaction processing system is a type of information system. TPSs collect, store, modify, and retrieve the transactions of an organization. <br />A transaction is an event that generates or modifies data that is eventually stored in an information system. <br />The essence of a transaction program is that it manages data that must be left in a consistent state. E.g. if an electronic payment is made, the amount must be both withdrawn from one account and added to the other; it cannot complete only one of those steps<br />
  13. 13. Single-User System<br />centralized system<br />DBMS<br />presentation application<br />services services<br />user module<br />Presentation Services - displays forms, handles flow of information to/from screen<br />Application Services - implements user request, interacts with DBMS<br />ACID properties automatic (isolation is trivial) or not required (this is not really an enterprise)<br />
  14. 14. Centralized Multi-User System<br />Dumb terminals connected to mainframe<br />Application and presentation services on mainframe<br />ACID properties required<br />Isolation: DBMS sees an interleaved schedule<br />Atomicity and durability: system supports a major enterprise<br />Transaction abstraction, implemented by DBMS, provides ACID properties<br />
  15. 15. Centralized Multi-User System<br />communication<br />central machine<br />presentation application<br />services services<br />• • •<br />DBMS<br />presentation application<br />services services<br />user module<br />dumb terminal<br />
  16. 16. Transaction Processing in a Distributed System<br />Decreased cost of hardware and communication make it possible to distribute components of transaction processing system<br />Dumb terminal replaced by computers<br />Client/server organization generally used<br />
  17. 17. Two-Tiered Model of TPS<br />database server<br />machine<br />client machines<br />presentation application<br />services services<br />• • •<br />DBMS<br />presentation application<br />services services<br />communication<br />
  18. 18. Three-Tiered Model of TPS<br />database server<br />machine<br />application server<br />machine<br />client machines<br />presentation<br />server <br />DBMS<br />• • •<br />application<br />server<br />presentation<br />server<br />communication<br />
  19. 19. features<br />Rapid response<br />Reliability<br />Inflexibility<br />Controlled processing <br />
  20. 20. types<br />Batch processing<br />Real time processing<br />
  21. 21. references<br />WamanJawadekar, "Management Information Systems Text & Cases- A Digital Firm Perspective” , 4th Edition, Tata McGraw-Hill Education Private Limited.<br />Tushar B Kute,<br />Sandip Institute of Technology & <br />Research Centre, Nashik<br />tbkute@gmail.com<br />