Chapter 12 - View design and integration. This chapter extends your database design skills by demonstrating an approach to analyze views and integrate user views into a complete, conceptual schema. This approach is an applications-oriented approach appropriate for designing complex databases. | Chapter 12 View Design and Integration This chapter describes the practice of designing user views and combining user views into a complete conceptual design. Objectives: - Understand the motivation for view design and integration - Analyze a form and construct an ERD to represent it - Determine an integration strategy for a database development effort - Perform both incremental and parallel integration approaches - Recognize and resolve synonyms and homonyms in the view integration process Outline Motivation for view design and integration View design with forms View integration Motivation: - View design and integration as way to manage complexity - Nature of large-scale database development efforts View design with forms - Hierarchical representation of forms - Analysis steps - Analysis of M-way relationships View integration: - Incremental vs. Parallel integration - Determining an integration strategy - Practice on a small example Motivation Database complexity reflects organizational complexity. Time-consuming and labor-intensive process Collect requirements from different user groups Coordination among designer team members Manage complexity of large designs The company size is an important determinant of complexity. Large organizations have many databases with individual databases supporting groups of functions such as payroll, personnel, accounting, material requirements, and so on. These individual databases can be very complex, as measured by the size of the ERDs. When converted to a relational database, the database can have hundreds to perhaps thousands of tables. Other measures of complexity involve the use of the database through forms, reports, computer programs, and validation rules. A large database can have hundreds to thousands of forms, reports, computer programs, and validation rules. The design effort often involves collecting requirements from many different groups of users. Requirements can be notoriously difficult to . | Chapter 12 View Design and Integration This chapter describes the practice of designing user views and combining user views into a complete conceptual design. Objectives: - Understand the motivation for view design and integration - Analyze a form and construct an ERD to represent it - Determine an integration strategy for a database development effort - Perform both incremental and parallel integration approaches - Recognize and resolve synonyms and homonyms in the view integration process Outline Motivation for view design and integration View design with forms View integration Motivation: - View design and integration as way to manage complexity - Nature of large-scale database development efforts View design with forms - Hierarchical representation of forms - Analysis steps - Analysis of M-way relationships View integration: - Incremental vs. Parallel integration - Determining an integration strategy - Practice on a small example Motivation Database complexity .
