Lesson 1

At this point in the course, you have learned enough to begin translating concepts into an entity–relationship (ER) diagram. In this module you will:

1. Learn the conventions for diagramming entities and their attributes.
2. Understand how to represent the three fundamental types of relationships: 1:1, 1:N, and M:N.
3. Recognize the symbols used to indicate mandatory and optional participation in relationships.

The term constructs is used here in its general sense, referring to the set of symbols and diagramming conventions employed in ER diagrams. Your course project will culminate in creating a complete ER diagram for Stories on CD, Inc.

Conceptual modeling is a critical step in database design. It focuses on describing the meaning of the data and its relationships before implementation. A database application is more than a collection of tables, it includes the programs and interfaces that allow users to interact with the data. For example, a banking application that tracks customer accounts must support operations such as deposits and withdrawals, each implemented as a controlled update to the database.

Modern database applications almost always provide user-friendly interfaces, such as forms and menus. Although building and testing these programs is often considered part of software engineering, the quality of the underlying database design determines whether such applications can perform efficiently and reliably.

Many software design tools now integrate database design methods with general software engineering practices, since both disciplines are closely related. However, in this course we maintain a traditional focus: conceptual database design itself, separating database structures and constraints from application code.

We introduce the Entity–Relationship (ER) model, a high-level conceptual data model widely used for database applications. The ER model captures the essential entities, attributes, and relationships in a domain, and serves as a foundation for logical and physical design. Its notation, which consists of ER diagrams, provides a clear, visual representation that simplifies communication between database designers and stakeholders. Lesson 2 will expand on this notation in detail.

By the end of this module, you should be able to:

1. Explain the purpose of an entity–relationship (ER) diagram.
2. Distinguish between different types of ER diagrams.
3. Apply the standard conventions for diagramming entities and their attributes.
4. Use the correct constructs to represent 1:1, 1:N, and M:N relationships.
5. Interpret and apply symbols for mandatory versus optional participation.
6. Refine and revise an ER diagram after review with stakeholders.
7. Verbalize an ER diagram to describe the meaning of entities and their relationships.

The next lesson introduces the formal definition of an ER diagram and explains how it is used to illustrate data organization and relationships during the design phase of database development.