{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

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

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

View Full Document Right Arrow Icon
Chapter 6 Project Q&A Database Design
Image of page 1

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

View Full Document Right 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?
Image of page 2
Types of Design Bottom-up Top-down
Image of page 3

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

View Full Document Right Arrow Icon
Functional Requirements Final Information- Level Design Physical-level Design Process Final Database Structure Physical Constraints Information-level Design Process Database Design Process
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
Image of page 5

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

View Full Document Right 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
Image of page 6
Database Design Methodology (a little different from what is in textbook) 1.
Image of page 7

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

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

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern