Chapter 9 View Design and Integration. © 2001 The McGraw-Hill Companies, Inc. All rights reserved....

Chapter 9Chapter 9

View Design and Integration

© 2001 The McGraw-Hill

Companies, Inc. All rights reserved.

McGraw-Hill/Irwin

Outline Outline

Motivation for view design and integrationView design with formsView integration



McGraw-Hill/Irwin

Why View Design and Why View Design and IntegrationIntegration??Database complexity reflects

organizational complexityTime-consuming and labor-intensive

processCollect requirements from different user

groupsInvolves coordination among designer

team



McGraw-Hill/Irwin

Motivation for View Design and Motivation for View Design and IntegrationIntegration

As the “divide and conquer” strategy is used to manage complexity, View Design and Integration is an approach to managing complexity of the database design effort.



McGraw-Hill/Irwin

Overview of View Design and Overview of View Design and IntegrationIntegration

Viewdesign

Viewintegration

Views

Conceptual schema

InterviewsDocumentation

Proposedforms/reports

Conflictidentification

Conflictresolution



McGraw-Hill/Irwin

View Design with FormsView Design with Forms

Important source of database requirementsReverse the process described in the first

part of the bookDerive an ERD that is consistent with the

formFive step procedure



McGraw-Hill/Irwin

Sample Customer Order FormSample Customer Order Form

Order No: 1234 Order Date: 3/19/2000

Customer No: 1001 Customer Name: Jon Smith

Address: 123 Any Street

City: Seattle State: WA Zip: 98115

Salesperson No: 1001 Salesperson Name: Jane Doe

$5001

$1503

$1204

Unit PriceQuantity

R210

B138

M128

Product No

Table

Cabinet

Bookcase

Description

Customer Order Form

Parent(main form)

Child(subform)



McGraw-Hill/Irwin

Form AnalysisForm Analysis

Create an ERD to represent a formERD supports form and other anticipated

processingERD should be consistent with the formERD is a view of the database



McGraw-Hill/Irwin

Form Analysis StepsForm Analysis StepsStep 1: Defineform structure

Step 2: Identifyentity types

Step 3: Attachattributes

Step 4: Addrelationships

Step 5: Checkcompleteness and

consistency



McGraw-Hill/Irwin

Step 1: Define Form StructureStep 1: Define Form Structure

Construct a hierarchy that depicts the form structure.

Most forms consist of a simple hierarchy where the main form is the parent and the subform is the child.

Complex forms can have parallel subforms and more levels in the hierarchy.



McGraw-Hill/Irwin

Hierarchical Form StructureHierarchical Form StructureParent Node

Order NoOrder Date

Customer No., Customer NameAddress, City

State, ZipSalesperson No

Salesperson Name

Child NodeProduct NoDescription

QuantityUnit Price



McGraw-Hill/Irwin

Step 2: Identify Entity TypesStep 2: Identify Entity Types

Split each node in the hierarchical structure into one or more entity types.

Make an entity type if the form field is a potential primary key and there are other associated fields in the form.



McGraw-Hill/Irwin

Entity Types for the Customer Entity Types for the Customer Order FormOrder Form

OrderOrder No

CustomerCustomer No

ProductProduct No

SalesPersonSalesPerson No



McGraw-Hill/Irwin

Step 3: Attach AttributesStep 3: Attach Attributes

Attach attributes to the entity types identified in the previous step

Group together fields that are associated with the primary keys found in Step 2

Form fields close together may belong in the same entity type



McGraw-Hill/Irwin

Attributes Added to the Entity Types Attributes Added to the Entity Types

OrderOrder No

Order Date

CustomerCustomer No

Customer NameAddress

CityStateZip

ProductProduct NoDescriptionUnit Price

OrderLineQuantity

SalesPersonSalesPerson No

SalesPerson Name



McGraw-Hill/Irwin

Step 4: Add RelationshipsStep 4: Add Relationships

Relationships involving the form entity type– Form entity type contains the form's primary key– Relationships between the form entity type and

other entity types derived from the parent node: usually 1-M.

– Add a relationship to connect the form entity type to an entity type in the child node

Add relationships to connect entity types derived from the child node if not already connected



McGraw-Hill/Irwin

Entity Relationship Diagram Entity Relationship Diagram

Customer NoCustomer NameAddressCityStateZip

Customer

Order NoOrder Date

Order

Product NoDescriptionUnit Price

Product

SalesPerson NoSalesPersonName

Salesperson

Makes

Takes

Contains

Quantity



McGraw-Hill/Irwin

Step 5: Check Completeness Step 5: Check Completeness and Consistencyand ConsistencyCheck the ERD for consistency and

completeness with the form structure.The ERD should contain minimum and

maximum cardinalities for all relationships, a primary key for all entity types, and a name for all relationships.



McGraw-Hill/Irwin

Consistency Rules for Consistency Rules for Relationship CardinalitiesRelationship Cardinalities1. In at least one direction, the maximum

cardinality should be one for relationships connecting entity types derived from the same node (parent or child).

2. In at least one direction, the maximum cardinality should be greater than one for relationships connecting entity types derived from nodes on different levels of the form hierarchy.



McGraw-Hill/Irwin

Analysis of M-Way Analysis of M-Way Relationships using FormsRelationships using FormsChoice between M-way and binary

relationships can be difficult.Data entry forms provide a context to

understand M-way relationships.An M-way relationship may be needed if a

form shows a data entry pattern involving three entity types.



McGraw-Hill/Irwin

Sample Project Purchasing Sample Project Purchasing FormForm

Project Purchasing Form

Purchase No.: P1234 Purchase Date: 3/19/2000

Project No.: PR1 Project Manager: Jon Smith

Part No. Supplier No. Quantity Unit Price

M128 S100 4 $120

M128 S101 3 $150

R210 S102 1 $500



McGraw-Hill/Irwin

ERD for the Project Purchase ERD for the Project Purchase FormForm

PartNoPartName

PartSuppNoSuppName

SupplierProjNoProjName

Project

QtyPrice

IncludesPartUses

SuppUses

PurchaseNoPurchaseDate

Purchase

PurchUses

Makes



McGraw-Hill/Irwin

Sample Purchasing FormSample Purchasing Form

Purchasing Form

Purchase No.: P1234 Purchase Date: 3/19/2000

Supplier No.: S101 Supplier Name: Anytime Supply

Part No. Quantity Unit Price

M128 4 $120

M129 3 $150

R210 1 $500



McGraw-Hill/Irwin

ERD for the Purchasing FormERD for the Purchasing Form

PartNoPartName

Part

SupplierNoSupplierName

Supplier

QtyPrice

Includes

PartUses

PurchaseNoPurchaseDate

Purchase

PurchUse

From



McGraw-Hill/Irwin

View IntegrationView Integration

Combine individual views into a complete database design

Incremental and parallel integration approaches



McGraw-Hill/Irwin

Incremental ApproachIncremental Approach

Incremental viewintegration

Integrated ERD(Views 1 to n)

View nPartially Integrated ERD



McGraw-Hill/Irwin

Parallel ApproachParallel Approach

Parallel viewintegration

Integrated ERD(Views 1 to n)

View nERD

View 1ERD

...



McGraw-Hill/Irwin

Integration StrategyIntegration Strategy

Parallel viewintegration

Integrated ERD

Partially integratedERD for subset 1 ...



Partially integratedERD for subset n

View subset 1 View subset n...



McGraw-Hill/Irwin

Precedence RelationshipsPrecedence Relationships

Form A precedes form B if form A must be complete before form B

Preceding forms typically provide data for subsequent forms

Place forms with precedence relationships in the same view subset



McGraw-Hill/Irwin

Precedence ExamplePrecedence Example

Customerform

Productform

Orderform

Invoiceform

Product Designform

Product Mftg.form



McGraw-Hill/Irwin

Resolving Synonyms and Resolving Synonyms and HomonymsHomonymsSynonym: spelled differently but have the

same meaningHomonym: same sound and often the same

spelling but different meaningForms provide a context to resolveMajor part of standardizing a vocabulary

View Integration ExamplesView Integration Examples



McGraw-Hill/Irwin

Sample Invoice FormSample Invoice FormINVOICE FORM

Customer No.: 1273 Invoice No.: 06389 Name: Contemporary Designs Date: 3/28/2000

Address: 123 Any Street Order No.: 61384

City: Seattle State: WA Zip: 98105

Product No Description Qty Ord

Qty Ship

Qty Back

Unit Price

Total Price

B381 Cabinet 2 2 150.00 300.00

R210 Table 1 1 500.00 500.00

M128 Bookcase 4 2 2 200.00 400.00

Total Amount $1200.00

Discount 60.00

Amount Due $1140.00



McGraw-Hill/Irwin

Incremental Integration Incremental Integration ExampleExample The following 5 slides

demonstrate the Incremental Integration process by integrating the Invoice Form with the ERD for Customer Order Form.



McGraw-Hill/Irwin

Form HierarchyForm Hierarchy

Parent NodeInvoice No

DateCustomer No.

Name, AddressCity, State, Zip

Order No., Discount

Child NodeProduct NoDescription

Qty Ord, Qty ShipQty Back

Unit Price, Total Price



McGraw-Hill/Irwin

Identify entity typesIdentify entity types and attach and attach attributesattributes

OrderOrder No

CustomerCustomer No

NameAddress

City, State, Zip

ProductProduct NoDescriptionUnit Price

ShipLineQty Ord.Qty Ship

Qty Back *Total Price *

InvoiceInvoice No.

DateTotal Amount *

Discount *Amount Due *



McGraw-Hill/Irwin

List the form fields that match existing List the form fields that match existing entity typesentity types

Order No matches the Order entity type.

Customer No, Customer Name, Address, City, State, and Zip match the Customer entity type.

Product No, Description, and Unit Price match the Product entity type.



McGraw-Hill/Irwin

Analyze homonymsAnalyze homonyms

Revise the Customer entity type with two sets of address fields: billing address fields and shipping address fields.

Add shipping address fields to the Invoice entity type.

Create a new entity type (ShipAddress) with the shipping address fields.



McGraw-Hill/Irwin

Integrated ERD (incremental)Integrated ERD (incremental)


Customer

Order NoOrder Date

OrderQuantity

OrderLine


Product

SalesPerson NoSalesPerson Name

SalesPerson

Makes

Takes

Contains

UsedIn

Invoice NoDateShipAddrShipCityShipStateShipZipTotal AmountDiscountAmount Due

Invoice

Qty ShipQty OrdQty Back

ShipLine

ShipFor

ShipsIn

UsesProd



McGraw-Hill/Irwin

Parallel Integration ExampleParallel Integration Example The difference between the

parallel and incremental approaches is that integration occurs later in the parallel approach.

For the parallel approach, ERDs for forms must be constructed before merging.



McGraw-Hill/Irwin

ERD for the Invoice FormERD for the Invoice Form


Customer

Order No

OrderQty ShipQty OrdQty Back

ShipLine


Product

Invoice NoDateTotal AmountDiscountAmount Due

Invoice

UsesProd

ShipFor ShipsIn

SentTo



McGraw-Hill/Irwin

Integrated ERD (Parallel)Integrated ERD (Parallel)


Customer

Order NoOrder Date

OrderQuantity

OrderLine


Product

SalesPerson NoSalesPerson Name

SalesPerson

Makes

Takes

Contains

UsedIn

Invoice NoDateShipAddrShipCityShipStateShipZipTotal AmountDiscountAmount Due

Invoice

Qty ShipQty OrdQty Back

ShipLine

ShipFor

ShipsIn

UsesProd



McGraw-Hill/Irwin

SummarySummary

View design and integration is an important skill for designing large databases.

Manage complexity of large development efforts.

The result of form analysis is an ERD that is a view of the database.

Two approaches for View Integration, incremental and parallel.

Date post:	13-Jan-2016
Category:	Documents
Upload:	shanna-wilson
View:	217 times
Download:	0 times

Chapter 9 View Design and Integration. © 2001 The McGraw-Hill Companies, Inc. All rights reserved....

Documents