List of Figures

• 1-1. A relational database with two tables: People and Movies.
• 1-2. The user interface of the SQL DBMS "Microsoft Access".
• 1-3. The user interface of the SQL DBMS "DB Browser for SQLite".
• 2-1. The user interface of the key-value data management app for the operation Add.
• 2-2. The user interface of the key-value data management app for the operation Delete.
• 2-3. The user interface of the key-value data management app for the operation Update.
• 3-1. The relationship data: which people are actors in which movies.
• 3-2. The contents of the SQLite movie database
• 3-3. The data about which people are actors in which movies.
• The information modeling process: from a conceptual model via design to class and table models.
• 4-1. The entity type movies represented as a class.
• 4-2. The entity type "movies" with a multi-valued attribute "genres".
• 4-3. The attribute "birth date" is mandatory, while "death date" is optional..
• 4-4. An association assigning a director to a movie and, the other way around, one or more movies to a director.
• 4-5. An exemplar model showing a director linked to three movies.
• 4-6. An association assigning zero or more actors to a movie and, the other way around, one or more movies to an actor.
• 4-7. An association class defining the role played by an actor in a movie.
• 4-8. An exemplar model showing an actor playing in two movies.
• 4-9. A functional association having also a name for its inverse.
• 4-10. Moons orbit planets, and, inversely, planets are orbited by moons.
• 4-11. People buy from companies, and, inversely, companies sell to people.
• 4-12. The entity types TV episodes and biographies specialize the entity type movies, thus inheriting its attributes.
• 4-13. The entity type "movies" is associated with the entity types "directors" and "actors".
• 4-14. The entity types "directors" and "actors" have been generalized by the entity type "people".
• 4-15. The segmentation of movies into TV episodes and biographies is disjoint, but incomplete.
• 4-16. The segmentation of customers into private customers and corporate customers is a partition.
• 4-17. A hierarchy of vehicle types with three segmentations.
• 5-1. Converting natural names to OOP names.
• 5-2. Replacing the attribute name "social security no." by "socSecNo".
• 5-3. Adding range definitions for all attributes.
• 5-4. Adding specific range definitions.
• 5-5. A design model class with two unique (or key) attributes.
• 5-6. A class with a (mandatory) standard ID attribute isbn and an optional unique attribute doi.
• 5-7. The entity types "Director" and "Actor" inherit the standard ID attribute "socSecNo" from "Person".
• 7-1. In MS Access repräsentiert eine Beziehung zwischen zwei Tabellen eine Fremdschlüssel-Abhängigkeit
• 9-1. Replacing platform-independent datatype names with SQL datatype names
• 9-2. Eliminating multi-valued attributes
• 9-3. Turning an enumeration datatype into an «enumeration table» class
• 9-4. Handling an enumeration datatype in MySQL
• 9-5. Eliminating a functional association
• 9-6. Eliminating a many-to-many association
• 9-7. Eliminating a generalization relationship
• 9-8. The table class Person
• 9-9. The gender foreign key dependency