KM_Pres_PA_Ch6

KM_Pres_PA_Ch6 - Chapter 6 Project Q&A Database Design Some...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 6 Database Design
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Some Definitions and Review Book’s Def.: A user view is the set of requirements that are needed to support a particular database user. Easier to think of it as individual tasks that a user needs to perform Remember that a user does not have to be a person – it can be a program that runs against data or sends data to another location Why do we work with user views instead of just doing it all at one time? What is a user view?
Background image of page 2
Types of Design Bottom-up Top-down
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Functional Requirements Final Information- Level Design Physical-level Design Process Final Database Structure Physical Constraints Information-level Design Process Database Design Process
Background image of page 4
Functional Requirements All inputs to and outputs from the system All reports that must be produced All inquiries that must be supported All other outputs that must be sent to other systems or to external destinations All update transactions that must be processed All calculations that must be performed All restrictions that the system must enforce All synonyms that are used for each attribute
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Information-level Design Result of this process is a logical design that cleanly supports the user requirements and is independent of any particular DBMS. All user functional requirements must be supported by this logical design. Enforce as many requirements as possible with the logical design—avoid having to write programs to enforce requirements whenever possible Should be in 3NF or 4NF unless excellent reason for 1NF or 2NF
Background image of page 6
Database Design Methodology (a little different from what is in textbook) 1. Identify an individual user view (requirement) and represent it as a
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/16/2008 for the course BA 105W taught by Professor Mohle during the Spring '08 term at CSU Fresno.

Page1 / 19

KM_Pres_PA_Ch6 - Chapter 6 Project Q&A Database Design Some...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online