Download Chapter 10: Database Application Design

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

page
1
page
2
page
3
page
4
page
5
page
6
page
7
page
8
page
9
page
10
page
11
page
12
page
13
page
14
page
15
page
16
page
17
page
18
page
19
page
20
page
21
page
22
page
23
Document related concepts
no text concepts found
Transcript 
Database Processing
Chapter 10
Database Application Design
David M. Kroenke
© 2000 Prentice Hall
Functions of a Database
Application
Page 238
Figure 10-1
© 2000 Prentice Hall
Chapter 10
CRUD
“the first function of a database
application is to CRUD views”
• Create
• Read
• Update
• Delete
Page 237
© 2000 Prentice Hall
Chapter 10
Format or Materialize views
“the second function of a database
application; the appearance of the
content”
Page 238
© 2000 Prentice Hall
Chapter 10
Other database functions
• Enforce constraints
• Provide for security and control
• Execute business logic
Page 238
© 2000 Prentice Hall
Semantic Object
Page 240
Figure 10-3a
© 2000 Prentice Hall
E-R Diagram
Page 240
Figure 10-3b
© 2000 Prentice Hall
Relational Design
Page 240
Figure 10-3c
© 2000 Prentice Hall
Relational Design
(w/ Surrogate Keys)
Page 240
Figure 10-3d
© 2000 Prentice Hall
Relational Diagram
Page 241
Figure 10-3e
© 2000 Prentice Hall
Chapter 10
View
“A structured list of data items
(attributes) from the entities or
semantic objects defined in the data
model”
A view can be materialized or
formatted as a form or report
Page 242
© 2000 Prentice Hall
Chapter 10
Recordset
“the result of an SQL statement”
Page 243
© 2000 Prentice Hall
Chapter 10
CRUD actions on a view
Read
SELECT CUSTOMER.CustomerID,
CUSTOMER.Name
FROM CUSTOMER, WORK
WHERE CUSTOMER.CustomerID =
WORK.CustomerID
Page 243
© 2000 Prentice Hall
Chapter 10
CRUD actions on a view
Create
INSERT INTO CUSTOMER
(CUSTOMER.Name, CUSTOMER.City)
VALUES (NewCust.CUSTOMER.Name,
NewCust.CUSTOMER.City)
Page 244
© 2000 Prentice Hall
Chapter 10
CRUD actions on a view
Update
INSERT INTO CUSTOMER
(CUSTOMER.Name, CUSTOMER.City)
VALUES (NewCust.CUSTOMER.Name,
NewCust.CUSTOMER.City)
Page 246
© 2000 Prentice Hall
CRUD actions on a view
Delete
Cascading deletions depends on
relationship cardinality
Page 247
Figure 10-6
© 2000 Prentice Hall
Chapter 10
Form
“a screen display used for data entry and
edit”
Forms should...
• reflect the view structure
• make data associations graphically clear
• encourage appropriate action
Page 248
© 2000 Prentice Hall
Chapter 10
Forms in a GUI Environment
• Drop-down list
• Option buttons in groups
• Check boxes
Page 251
© 2000 Prentice Hall
GUI controls
Page 252
Figure 10-10
© 2000 Prentice Hall
Chapter 10
Report Design
Reports should...
• reflect the structure of the
underlying view
• handle implied objects
Page 253
© 2000 Prentice Hall
Chapter 10
Enforcing Constraints
• Domain
• Uniqueness
• Relationship
Cardinality
Page 256
• 1.1 and 1.N
– fragments
– orphans
• Business Rule
– triggers
© 2000 Prentice Hall
Chapter 10
Security
• Horizontal
• Vertical
Page 264
© 2000 Prentice Hall
Chapter 10
Control
• System of menus
• Transaction boundaries
Page 265
© 2000 Prentice Hall
Related documents