The document discusses conceptual database design, which involves constructing an entity-relationship (ER) model from system requirements. This involves creating a pictorial representation of entities (objects with attributes) and their relationships using an ER diagram. The model is then checked for redundancy and validated against user transactions to ensure all scenarios are supported.
The document discusses conceptual database design, which involves constructing an entity-relationship (ER) model from system requirements. This involves creating a pictorial representation of entities (objects with attributes) and their relationships using an ER diagram. The model is then checked for redundancy and validated against user transactions to ensure all scenarios are supported.
The document discusses conceptual database design, which involves constructing an entity-relationship (ER) model from system requirements. This involves creating a pictorial representation of entities (objects with attributes) and their relationships using an ER diagram. The model is then checked for redundancy and validated against user transactions to ensure all scenarios are supported.
The requirements analyzed in the previous step is converted into conceptual model. It is a process of constructing a data model for each view of the real world problem which is independent of physical considerations. This step involves: 1. Constructing the ER Model 2. Check the model for redundancy 3. Validating the model against user transactions to ensure all the scenarios are supported. ER Modeling: 1. Pictorial Representation of the Real world problem in terms of entities (which have attributes) and relations between the entities is referred as ER diagram. 4. Entities: An entity is a class of distinct identifiable objects or concepts 5. Relations: Associations among entities is referred as Relations 6. Attributes: Attributes are properties or characteristics of entities.