0% found this document useful (0 votes)
14 views4 pages

Dbms A

Uploaded by

shuvronil562
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views4 pages

Dbms A

Uploaded by

shuvronil562
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

What are the key benefits of using conceptual data models in the early stages of
database development?

❖ Conceptual data models can help in the early stages of database development by:

Defining project scope

A conceptual model can help stakeholders understand what’s needed to achieve business
goals.

Sharing understanding

A conceptual model can help create a shared understanding of the business by capturing
essential concepts.

Visualizing data

Data modeling can help visualize data relationships and structures, which can improve
data understanding.

Identifying issues

Data modeling can help identify redundant or missing data, and set up monitoring to
ensure data quality.

2.Explain the difference between strong entities and weak entities

❖ A “strong entity” in an Entity Relationship Diagram (ERD) is an independent entity


that can exist on its own and has a complete primary key to uniquely identify each
instance, while a “weak entity” is dependent on another entity (called the identifying
owner) for its existence and cannot have a complete primary key without including
the identifier of the strong entity it relies on.

3.What is a derived attribute, and how is it typically represented in a data model?

❖ A derived attribute is a type of attribute where the value for that attribute will be
derived from one or more of the other attributes of the same database.

4.Why is it important to specify cardinality in a relationship?


❖ Cardinality of a relationship is the number of tuples (rows) in a relationship. It is a
fundamental concept that helps define how data in different tables connect and
how many unique entries exist in a particular column.

5.How do you represent a multivalued attribute in an E/R diagram?

❖ In an entity-relationship (ER) diagram, a multivalued attribute is represented by a


double oval:
A multivalued attribute is an attribute that can have more than one value for a single
instance of an entity. For example, a person can have more than one phone number,
so the phone number attribute is multivalued.

6.How does an ER diagram help in visualizing a database design?

❖ An ER diagram (Entity Relationship Diagram) helps visualize a database design by


providing a graphical representation of how different entities (tables) within a
database are related to each other.

7.What is a “many-to-many” cardinality constraint, and how is it represented in ER


diagrams?

❖ A many-to-many cardinality constraint in an Entity Relationship (ER) diagram


represents a relationship between two entities where each entity can have multiple
instances involved in the relationship.

8.Provide an example of a weak entity and explain its relationship to a strong entity.

❖ A good example of a weak entity is a “room” in a database representing a building;


the “room” can only exist within the context of a “building” (strong entity), meaning it
cannot be uniquely identified without reference to the building it belongs to, making
it dependent on the strong entity for its existence.

9.Explain the representation of a ternary relationship in an EER diagram

❖ In an Entity-Relationship (ER) diagram, a ternary relationship is represented by a


diamond shape connecting three entities, signifying a relationship that involves
three different entity types simultaneously; essentially, it shows how instances of
three entities can be related to each other in a single connection.

10.What is an entity in ER modeling, and how does it differ from an attribute?

❖ In entity-relationship (ER) modeling, an entity is a real-world object or concept that


can have data stored about it, while an attribute is a property or characteristic of
that entity:

Entity

An entity is a fundamental unit that represents a real-world concept, such as a


person, location, or idea. Entities are the most important elements of a data model,
and they can have one or more attributes. For example, a customer entity might
have attributes such as name, email, and address.

Attribute

An attribute is a property or characteristic that describes an entity. For example, age


is an attribute that can be derived from a person’s date of birth. In ER diagrams,
attributes are represented as ovals and connected to an entity or relationship set.

11.What is the role of subclasses in the Enhanced ER model ?

❖ In the Enhanced Entity-Relationship (EER) model, subclasses play a key role in


creating a hierarchical structure of entities:

Inheritance

Subclasses inherit attributes and relationships from their superclass, and can also
define their own attributes and relationships.

Specialization

Subclasses are defined from a superclass to identify sub-groups within an entity


set. For example, an employee can be further grouped into subclasses such as
secretary, engineer, or technician.

Generalization

A superclass is defined from two or more subclasses.

Representation
In ER diagrams, specialization/generalization relationships are commonly represented
using a diamond notation.

Membership

An entity cannot exist in a database if it only belongs to a subclass, it must also


belong to the superclass.

13.What is the concept of UNION types, and how are they represented in the Enhanced
ER model?

❖ Union Types: E ER model allows for the creation of a union type, which is a
combination of two or more entity types. The union type can have attributes and
relationships that are common to all the entity types that make up the union.

You might also like