Data Modeling and ERDs
42 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to Lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What does a data model primarily represent?

  • The physical location of data storage devices.
  • The network infrastructure used to transmit data.
  • The programming languages used to manipulate data.
  • Data used and created by a business system. (correct)

Which of the following BEST describes the purpose of normalization in data modeling?

  • To document metadata within a data dictionary.
  • To graphically represent the data model using ERDs.
  • To validate the accuracy and structure of data models. (correct)
  • To balance data models with process models.

In the context of data modeling, what does an Entity Relationship Diagram primarily depict?

  • The relationships between entities in a database. (correct)
  • The security protocols for accessing the data.
  • The flow of data between different processes.
  • The physical storage structure of the data.

Data modeling is crucial because data is a ______ to be shared by as many processes as possible.

<p>resource (A)</p> Signup and view all the answers

What should data models balance with?

<p>Process models (A)</p> Signup and view all the answers

What is one of the listed learning objectives?

<p>Explain the rules and style guidelines for creating entity relationship diagrams (ERDs). (A)</p> Signup and view all the answers

What should data organization be?

<p>Flexible and adaptable to unanticipated business requirements (D)</p> Signup and view all the answers

What is the purpose of data modeling?

<p>To ensure data organization must be flexible and adaptable to unanticipated business requirements. (B)</p> Signup and view all the answers

What is the BEST definition of a data model?

<p>A formal way of representing the data that are used and created by a business system. (B)</p> Signup and view all the answers

What does the logical data model show?

<p>The organization of data without indicating how it is stored, created, or manipulated (D)</p> Signup and view all the answers

What process do analysts use to validate data models?

<p>Normalization (D)</p> Signup and view all the answers

Data models are typically ______ than process models and are constructed more ______.

<p>smaller, rapidly (A)</p> Signup and view all the answers

What do ERD symbols show?

<p>When one instance of an entity must exist for an instance of another to exist. (D)</p> Signup and view all the answers

If a 'chemical' must exist before chemical requests can be created for that chemical, which rule is being followed?

<p>Business rule (D)</p> Signup and view all the answers

What does it mean if ERD symbols can show when one instance of an entity can be related to only one or to many instances of another entity?

<p>It illustrates relationship cardinality. (D)</p> Signup and view all the answers

What does an entity represent in data modeling?

<p>A person, place, event, or thing about which data is collected. (A)</p> Signup and view all the answers

What is an attribute in the context of data modeling?

<p>Information captured about an entity. (A)</p> Signup and view all the answers

Which of the following is TRUE regarding attribute names?

<p>Attribute names should be nouns. (B)</p> Signup and view all the answers

Which is an example of a composite attribute?

<p>Address (A)</p> Signup and view all the answers

What is is called when an identifier consists of several attributes?

<p>A concatenated identifier (C)</p> Signup and view all the answers

In ER diagrams, what are relationships?

<p>Associations between entities (B)</p> Signup and view all the answers

What should the names of relationships be?

<p>Active verb names (C)</p> Signup and view all the answers

What is cardinality?

<p>The number of times instances one entity can be related to instances in another entity. (D)</p> Signup and view all the answers

In ERD, what is the purpose of modality?

<p>Indicating whether an instance of a child entity can exist without a related instance in the parent entity. (D)</p> Signup and view all the answers

What is the term for relationships that connect 2 entities?

<p>Binary Relationships (A)</p> Signup and view all the answers

What is a foreign key?

<p>The primary key of one entity that is contributed to another entity. (B)</p> Signup and view all the answers

What does the process of drawing ERDs involve?

<p>An iterative process of trial and revision. (A)</p> Signup and view all the answers

What should you do when building ERDs?

<p>Identify the entities. (B)</p> Signup and view all the answers

Which of the following is a guideline for ERD design?

<p>Avoid unnecessary attributes. (D)</p> Signup and view all the answers

Data stores of DFD generally correspond to what?

<p>Entities (A)</p> Signup and view all the answers

When should entities associated with implementation of the system be added to the ERD?

<p>They will be added later. (B)</p> Signup and view all the answers

In data modeling, what does 'balancing ERDs with DFDs' ensure?

<p>All data stores and elements correspond between models. (D)</p> Signup and view all the answers

What do process models contain?

<p>Data flows and data stores (C)</p> Signup and view all the answers

What does checking that all data stores and elements correspond between models ensure?

<p>Data that is not used is unnecessary (A)</p> Signup and view all the answers

In the context of normalization, what does the '0 Normal Form' primarily address?

<p>Removing the repeating attributes and repeating groups. (D)</p> Signup and view all the answers

What is the primary goal of achieving '3 Normal Form' (3NF) in database normalization?

<p>To ensure that all non-key attributes are fully dependent on the primary key and independent of each other. (C)</p> Signup and view all the answers

In the context of Entity Relationship Diagrams (ERDs), consider two entities: 'Customer' and 'Order'. A customer can place multiple orders, but each order belongs to only one customer. What type of relationship exists between 'Customer' and 'Order'?

<p>One-to-many (C)</p> Signup and view all the answers

Consider a database used in a university. There are entities for 'Students', 'Courses', and a relationship between them indicating which students are enrolled in which courses. If multiple students can enroll in multiple courses, what type of relationship should be modeled in the ERD?

<p>Many-to-many (A)</p> Signup and view all the answers

Imagine a scenario where you are designing a database for a library. You have an entity called 'Book' with attributes like 'Title', 'Author', and 'ISBN'. Which of the following represents a multi-valued atribute?

<p>Genre (a book can belong to multiple genres) (D)</p> Signup and view all the answers

In designing a database for a hospital, one entity is 'Patient'. Each patient is assigned a unique 'PatientID'. Additional information, such as 'Name', 'DateOfBirth', and 'Address' are also stored. If the hospital wants to ensure that every patient record is uniquely identifiable, and no two patients can have the same ID, what type of key should 'PatientID' be?

<p>Primary Key (B)</p> Signup and view all the answers

A company decides to implement a database system to manage its employees and departments. Each department has a unique 'DepartmentID', and each employee is assigned to one department. The 'Employee' entity contains attributes like 'EmployeeID', 'Name', and 'DepartmentID'. In this scenario, what is 'DepartmentID' in the 'Employee' entity?

<p>Foreign Key (B)</p> Signup and view all the answers

Consider two entities in a university database: 'Professor' and 'Course'. A professor can teach multiple courses. The database design evolves, and it's decided that a professor can specialize in multiple areas (e.g., 'Databases', 'AI', 'Networking'). What type of relationship needs to be modeled between 'Professor' and 'Specialization'?

<p>Many-to-many (A)</p> Signup and view all the answers

Flashcards

Data Model

A formal way of representing the data used and created by a business system.

Logical data model

Shows the organization of data without indicating how it is stored, created, or manipulated.

Physical data model

Shows how the data will actually be stored in databases or files.

Entity Relationship Diagram (ERD)

A popular way to depict the data model.

Signup and view all the flashcards

Normalization

The process analysts use to validate data models.

Signup and view all the flashcards

Business rules

Constraints that are followed when the system is in operation.

Signup and view all the flashcards

Entity

A person, place, event, or thing about which data is collected

Signup and view all the flashcards

Attributes

Information captured about an entity.

Signup and view all the flashcards

Composite Attribute

Address consisting of Street, City, State and Zip

Signup and view all the flashcards

Multi-valued attribute

Attribute that may have more than one value for a single entity instance.

Signup and view all the flashcards

Derived Attribute

An attribute whose value can be calculated from other values.

Signup and view all the flashcards

Identifier

One or more attributes that uniquely identify each entity instance.

Signup and view all the flashcards

Relationships

Associations between entities.

Signup and view all the flashcards

Parent entity

The first entity in the relationship

Signup and view all the flashcards

Child entity

The second entity in the relationship

Signup and view all the flashcards

Cardinality

Refers to the number of times instances one entity can be related to instances in another entity

Signup and view all the flashcards

One-to-one (1:1)

One instance in an entity refers to one and only one instance in the related entity.

Signup and view all the flashcards

One-to-many (1:N)

One instance in an entity refers to one or more instances in the related entity.

Signup and view all the flashcards

Modality

Refers to whether an instance of a child entity can exist without a related instance in the parent entity

Signup and view all the flashcards

Not Null

an instance in the related entity must exist for an instance in another entity to be valid

Signup and view all the flashcards

Null

no instance in the related entity is necessary for an instance in another entity to be valid

Signup and view all the flashcards

Foreign Keys

A relationship implies that instances of one entity are related to instances of another entity

Signup and view all the flashcards

Design Guidelines

Best practices rather than rigid rules

Signup and view all the flashcards

Data Omission

Data that has been omitted results in an incomplete system

Signup and view all the flashcards

Study Notes

  • Data modeling is a way of representing the data used by a business system, showing people, places, and relationships.
  • Logical data models show data organization, whereas physical data models show data storage in databases or files.
  • Entity Relationship Diagrams (ERDs) are used to depict data models.
  • Normalization validates data models and data models should balance with process models.
  • Data modeling is crucial because data is a shared resource that must be flexible and adaptable and data structures are more permanent than the processes that use the data, similar to existing systems.
  • Data models are smaller and faster to construct than process models and data model construction helps analysts and users reach consensus on terminology and rules.

Entity Relationship Diagrams (ERDs)

  • ERDs describe the data.
  • Business rules are constraints followed during system operation and ERD symbols show when one entity instance must exist for another.
  • The symbols show when one entity instance relates to one or many instances of another.
  • They also indicate when an entity instance's existence is optional for a related entity instance.

Entities & Attributes

  • Entities are identified as the things of the data being collected.
  • Attributes are the information captured:
    • Only those by the organization should be included in the model, and attribute names are nouns.
    • Sometimes entity name is added at the beginning of the attribute name for clarity.
    • Attributes can be composite, multi-valued, or derived
  • Identifiers are the unique attributes of each entity instance, could be concatenated, artificial or a set of attributes.
  • A relationship is an association between entities (parent or child) using activeverb names going in both direction.
  • Cardinality refers to the number of times entities can be related.
  • Refers to number of instance one entity can be related to instances in another entity: one to one (1:1), one to many (1:N), many to many (M:N)
  • Modality is whether a child entity can exist without a related parent entity.
  • Foreign keys are primary keys migrated from one entity to another to identify relationships.
  • Binary relationships can have one-to-one or one-to-many relationships.

Creating an ERD

  • Drawing the ERD is iterative, complex, and includes:
    • Identify the entities
    • Add appropriate attributes for each entity
    • Draw the relationships that connect associated entities
  • To identify entities, look for major categories of information and inputs/outputs.
  • Appropriate Attribute Checklist:
    • Check process models for details on data flows and stores.
    • Check the data requirements of the requirement definition.
    • Interview knowledgeable users.
    • Perform a document analysis on existing forms and reports.
    • Select the entity's candidate identifier after this process.
  • To draw the relationships:
    • Start with an entity and identify all related entities.
    • Describe the relationship with a verb phrase.
    • Discuss business rules to determine cardinality and modality.
    • Data stores of the DFD generally correspond with entities. Only include multiple instance entities and implementation entities should be be added later.

Validating, Balancing, and Using a CRUD Matrix

  • Design Guidelines:
    • Best practices rather than rigid rules.
    • Entities = many occurrences.
    • Avoid unnecessary attributes, components are clearly labelled.
    • Correct cardinality and modality.
    • Break attributes into lowest level needed.
    • Labels should reflect common business terms.
    • Assumptions should be clearly stated
  • All analysis activities are interrelated.
  • Process models contain two major data components:
    • Data flows and Data stores
  • Many CASE tools provide features to check for imbalance
  • The DFD data components need to balance the ERD's data stores (entities) and data elements (attributes):
    • Unused data is unnecessary.
    • Omitted data can result in an incomplete system.
    • Check that the models make sense instead of thoughtlessly.

Normalization

  • Normalization includes multiple steps:
    • "0 Normal Form" requires repeating attributes and groups be removed, creating new entities and relationships.
    • "1 Normal Form" requires the removal of partial dependencies when the identifier is composed of >1 attribute.
    • "2 Normal Form" requires the removal of transitive dependencies or derived attributes.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Quiz Team

Related Documents

Description

Explore data modeling techniques for business systems, including logical and physical models. Learn about Entity Relationship Diagrams (ERDs) for data representation and normalization for validation. Understand the importance of data modeling in creating flexible and adaptable data structures.

More Like This

Use Quizgecko on...
Browser
Browser