TAILIEUCHUNG - Lecture Enterprise information systems: A pattern-based approach (3/e): Chapter 1 - Cheryl Dunn, J. Owen Cherrington, Anita Hollander

Chapter 1 - An introduction to integrated enterprise information systems. The objectives of this chapter are to provide a definition for integrated enterprise information systems, discuss the need for integrated information systems in enterprises, and assess the extent to which current enterprise information systems are integrated. | Chapter 1 An Introduction to Integrated Enterprise Information Systems Chapter Learning Objectives Define the phrase “integrated enterprise information system” Identify impediments to integrating the components of enterprise information systems Explain the need to eliminate stovepipes, in operations and in information systems Identify artifacts versus “natural” phenomena in enterprise activities as opportunities for effective re-engineering 1- What are Integrated Enterprise Information Systems? Enterprise A business, an industrious effort, especially one directed toward making money Information System A set of interconnected channels for communicating knowledge of specific events or situations Integrated Joined together, united, made into a whole by having brought all parts together 1- Degrees of Integration How can we use both of these toy trains to carry the same toy freight? (note the differences in connectors – we can’t simply unhook the freight car from one and attach it to the other) Unload freight from one train, re-load onto the other Too much work! Tie freight car from one to the other with string Unstable connection! Use special building block with Lego connector on one end, K’nex connector on other end Buy two special building blocks one with Lego connector on one end and generic connector on the other end One with K’nex connector on one end and generic connector on the other end 1- Aren’t all enterprise systems integrated? Enterprise “stove pipes” or “silos” As enterprises grow, they typically become divided based on functional areas Each functional area typically has its own system Even within functional areas, enterprises often develop different systems for different information needs If existing systems lack functionality, additional systems are built to satisfy new needs NO! Why Not? 1- Common Integration Attempts Integrate the end results Let each functional area have its own system and require them to submit end results in a .

• Quản trị kinh doanh
• Enterprise information systems
• Lecture Enterprise information systems
• Business process
• REA enterprise ontology
• Common integration attempts
• Ford motor company
• ERP systems
• Inter enterprise modeling
• Collection business process
• Enterprise value chains
• Enterprise value chain
• Conversion business process
• Enterprise system risks
• Risk assessment
• Information retrieval
• Relational databases
• Object patterns
• Business entrepreneur script
• Value chain modeling
• Value system
• Business process level modeling
• Conceptual modeling constructs
• Task level modeling
• System flowcharts
• Relational database design
• Payment business process
• REA acquisition
• View integration
• Implementation compromises
• Human resource business process
• Financing business process
• Financing cycle resources
• Information systems
• Lecture Information systems
• Enterprise applications
• Enterprise systems
• Business communications
• Enterprise resource planning
• Management information systems
• Introduction to management information systems
• Business information technology
• Problems of information silos
• Transaction processing
• Enterprise resource planning systems
• Accounting information systems
• Lecture Accounting information systems
• Hệ thống thông tin kế toán
• Business processes
• Business applications
• E business systems
• Enterprise business systems
• Lecture Management information systems
• Information systems in business
• Global management of information technology
• Organizing IT