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

Chapter 10 - View integration and implementation compromises. One objective of this chapter is to explain how to unite the business process level REA models for multiple transaction cycles. A second objective is to explain implementation compromises commonly made at each step in conceptual modeling and database design. A final objective of this chapter is to demonstrate retrieval of information from multiple integrated business processes. | Chapter 10 View Integration and Implementation Compromises Chapter Learning Objectives Identify the steps needed to integrate multiple business process level REA models Complete an integration of two or more business process level REA conceptual models Identify and create common conceptual level, logical level, and physical level implementation compromises Explain common reasons for compromising implementations Identify information needs that require information from multiple tables in multiple business processes Create queries to satisfy information needs that require information from multiple business processes 10- View Modeling and View Integration Recall that one reason we use models in designing information systems is to reduce complexity and to simplify the reality into manageable pieces. The separate modeling of each transaction cycle is called “view modeling”. Combining the models together to form a complete whole is called “view integration”. 10- View Integration Step 1: Identify the common entities in two conceptual level views Each pair of cycles that is connected in the value chain shares at least one common resource. Many cycles have at least one agent in common. Cash receipt events and Cash disbursement events exist in multiple cycles. 10- Step 2: Merge the common entities, resolving entity and attribute conflicts Entity name conflicts Synonyms: two or more different entity names used to represent the same entity Homonyms: one entity name used to represent two or more different entities Attribute conflicts Different attributes used to describe the same entity in various views Include all attributes needed for all transaction cycles as attributes for the entity in the integrated model View Integration 10- View Integration Step 3: Resolve relationship conflicts, including name conflicts and structural conflicts Ensure each relationship has a unique name Ensure cardinalities are appropriate for relationships once common entities are .

• Quản trị kinh doanh
• Enterprise information systems
• Lecture Enterprise information systems
• Business process
• REA enterprise ontology
• View integration
• Implementation compromises
• 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
• Common integration attempts
• Ford motor company
• 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
• 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