Summary of DM Chapter 1

1
Summary of DM Chapter 1
2
DMs perspective

• All information belongs in a database.
• If an organization can get the information into
  the database in a good fashion, then all will
  be well
• What good means is hinted at and will be the
  topic of the next 5 chapters along with how to
  go about getting to this goodness
• What is good changes as a company changes over
  time (I.e., reengineering, system integration,
  etc. are required periodically)

3
A comment

• Note that since 1995, it has become clear that
  knowledge management is important to
  organizations and most of the data relevant to it
  is stored in unstructured text (e.g., reports,
  presentations, videotaped meetings, etc.) Such
  information does not fit into a database as
  conceived here. This is why Google is making
  money and is not simply a part of Oracle.

4
What is Data Modeling?

• Again, we see an attempt to make an engineering
  process visible
• Figure 1.3 is an example of which SE approach?

5
Phases of Database design

• Conceptual database design
• Logical database design
• Physical database design
• We will focus on the first two in this class

6
Other stuff

• My homepage (under construction)
• http//mingo.info-science.uiowa.edu/light
• There is a pointer to last semesters class URL
• A current class URL will exist by next class
• Most of what is on last years URL will apply to
  this years class as well
• BUT not exactly and not everything