Held: ,

Back to Outline 10 - Modeling Basics. On to Outline 12 - Software as a Service.

Summary

We continue our exploration of data modeling by looking at a sample Web application.

Related Pages

Overview

• Data Modeling.
• Exercise: A Sample Database Design.
• Analysis.
• Revisions.

Administrivia

• I hope you had a good weekend.
• I spent Saturday at the second-year retreat and most of Sunday sick in bed, so I continue to be behind.
• Today will be one of those "Think about things and then report back" days.

Upcoming Work

• For Wednesday: No additional reading. Use the time to catch up in the two books!
• Reading Journal for Wednesday (due Tuesday at 10pm)
  • Subject: Reading Journal for Class 12 (Your Name)
  • Create what you think are appropriate models for alumni.grinnell.edu. (I'm okay if you describe them informally.) Make sure that you indicate relationships.

Good Things to Do

See http://www.cs.grinnell.edu/~rebelsky/s2d@g/

• Tuesday at noon: CS Table on IoT.
• Tuesday at 4:15 p.m. Thursday Extra on Robots.
• Thursday at 11:00 a.m. Convocation on Gates.
• Thursday at 4:15 p.m. Thursday Extra.

Data Modeling

• How do we generally model data in these kinds of applications? (Conceptually, rather than what code do we use.)
• We normally say that we use a "relational" model. What does "relation" mean here?
• What general kinds of relationships are there between relations? (and what are examples of each)?
• Why do we use a DBMS rather than managing things by ourselves?

An Exercise

• LibraryThing is a shared "keep track of my books" SaaS.
• For LibraryThing, what relations (tables) do you see as useful? How do you represent them?