Database Development Life Cycle Quiz
47 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

Which of the following phases is NOT part of the Systems Development Life Cycle (SDLC)?

  • System analysis
  • Integration and testing
  • Planning
  • System deployment (correct)

The Database Development Life Cycle (DBLC) consists of eight phases.

False (B)

What is the primary goal of the system development life cycle (SDLC)?

To produce a high-quality solution that meets client expectations.

The initial study in database development begins by examining the statement of __________.

<p>requirements</p> Signup and view all the answers

Match the following phases of the Database Development Life Cycle (DBLC) with their descriptions:

<p>Planning = Define problem and objectives Implementation and Loading = Develop and load the database Testing and Evaluation = Verify the database's functionality Operation and Maintenance = Ensure ongoing support and updates</p> Signup and view all the answers

Which statement best describes the initial study phase of database development?

<p>It produces a system specification based on the current situation. (B)</p> Signup and view all the answers

The objective of defining the scope and boundaries of a project is included in the initial study.

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

What is the primary focus of the initial study in database development?

<p>To analyze the company situation and collect requirements.</p> Signup and view all the answers

What is primarily tested during the evaluation phase of a database?

<p>Database performance, integrity, and security (C)</p> Signup and view all the answers

Once a database has passed the evaluation stage, it is considered operational.

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

What activities must the database administrator perform for routine maintenance?

<p>Preventive maintenance, corrective maintenance, adaptive maintenance, and managing access permissions.</p> Signup and view all the answers

The ___________ data model perceives the real world as consisting of entities described by attributes and relationships.

<p>entity-relationship</p> Signup and view all the answers

Which of the following is not a responsibility of the database administrator?

<p>Creating new user interfaces (B)</p> Signup and view all the answers

Match the following maintenance activities with their descriptions:

<p>Preventive maintenance = Backup and disaster recovery planning Corrective maintenance = Restoring data after a loss Adaptive maintenance = Improving database performance and adding new features Access permissions management = Controlling who can access what within the database</p> Signup and view all the answers

Data encryption is one of the security measures tested during the database evaluation phase.

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

What does the conceptual design of a database focus on?

<p>Discovering and analyzing organizational and user data requirements.</p> Signup and view all the answers

What is a composite attribute used for in a design schema?

<p>To refer to an entire attribute or its components (D)</p> Signup and view all the answers

A single-valued attribute can take multiple values for a specific occurrence of an entity.

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

What is an example of a multivalued attribute?

<p>customer_phone_number</p> Signup and view all the answers

A _____ attribute is calculated from other related attributes.

<p>derived</p> Signup and view all the answers

Which statement accurately describes a super key in database terms?

<p>A combination of attributes that uniquely identifies an entity occurrence (A)</p> Signup and view all the answers

Derived attributes are always stored in the database.

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

Match the following terms with their definitions:

<p>Single-valued attribute = An attribute with only one value for an entity occurrence Multivalued attribute = An attribute that can take multiple values for an entity occurrence Derived attribute = An attribute whose value is calculated from other attributes Super key = A set of attributes that can uniquely identify an entity occurrence</p> Signup and view all the answers

What represents a multivalued attribute in a schema diagram?

<p>Double oval</p> Signup and view all the answers

What is total generalization in the context of entity sets?

<p>Each higher-level entity occurrence must belong to a lower-level entity. (D)</p> Signup and view all the answers

In partial generalization, every entity occurrence in a higher-level entity set must belong to a lower-level entity set.

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

What symbol is used to represent total generalization in an E-R diagram?

<p>Double line connecting the higher-level entity set to the triangle symbol</p> Signup and view all the answers

An entity occurring as both a university staff and a university student is an example of _____ generalization.

<p>overlapping</p> Signup and view all the answers

Match the following concepts with their definitions:

<p>Total generalization = Each higher-level entity must belong to a lower-level entity. Partial generalization = Some higher-level entities may not belong to any lower-level entity. Aggregation = Represents relationships as higher-level entity sets. Participation constraints = Specifies entity occurrence requirements in subclasses.</p> Signup and view all the answers

Which of the following statements about aggregation is true?

<p>It allows treating a relationship set as an entity set for participation in other relationships. (A)</p> Signup and view all the answers

Completeness constraints only determine whether membership in lower-level sets is optional.

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

What defines a total participation constraint in a database context?

<p>Every entity in the higher-level set must be included in a lower-level set.</p> Signup and view all the answers

When should an address be modeled as an entity rather than an attribute?

<p>When there are multiple addresses per customer (B)</p> Signup and view all the answers

A product can be offered with multiple prices if price is modeled as an attribute.

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

What is a key consideration when deciding whether to model a concept as an entity or a relationship?

<p>The use and semantics of the data.</p> Signup and view all the answers

If you need to model multiple relationships between entities, it is often better to use ________ relationships instead of ternary relationships.

<p>binary</p> Signup and view all the answers

Match the following entities or concepts with their appropriate consideration:

<p>Address = Represented as an entity when multiple exist Price = Must be modeled as an entity for multiple prices Strong entity = Can exist independently Weak entity = Depends on another entity for identification</p> Signup and view all the answers

Which of the following is NOT a question to consider during ER design decision making?

<p>Should I use team collaboration? (D)</p> Signup and view all the answers

Using aggregation allows you to treat a set of entities and their relationships as a single unit.

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

When is it beneficial to use generalization in ER design?

<p>When there are common attributes among several entities.</p> Signup and view all the answers

What does total participation in a relationship indicate?

<p>All entities in the set must participate in the relationship. (D)</p> Signup and view all the answers

A weak relationship exists when a child entity's existence is independent of its parent.

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

What symbol is used to represent total participation in a relationship?

<p>Double lines or Bold line</p> Signup and view all the answers

Partial participation means that the participation of entity set E in relationship R is __________.

<p>optional</p> Signup and view all the answers

Which of the following best describes cardinality in relationships?

<p>Determines how many relationships can occur for an entity. (B)</p> Signup and view all the answers

Every loan entity must be linked to at least one customer through the borrows relationship.

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

What is an associative entity in relational and entity-relationship theory?

<p>It is a term used to describe a relationship between two or more entities.</p> Signup and view all the answers

Flashcards

Database Development Life Cycle (DBLC)

A structured approach to managing the development of a database, from initial planning to implementation, maintenance, and beyond.

Database Initial Study

This phase involves understanding the current system's strengths and weaknesses, identifying problems, and setting clear objectives for the new database.

Database Design

This phase focuses on creating a detailed blueprint of the database, defining entities, relationships, and data attributes.

Database Implementation and Loading

This phase involves physically creating the database, populating it with data, and testing its functionality. It includes all the developmental efforts of building the database

Signup and view all the flashcards

Database Testing and Evaluation

This phase involves rigorously testing the database for accuracy, performance, and security before final release.

Signup and view all the flashcards

Database Operation and Maintenance

This phase involves ongoing maintenance (updating data, resolving errors, and enhancing functionality) after the database is live.

Signup and view all the flashcards

System Specification

A formal description of what a system should do without specifying how it will be implemented.

Signup and view all the flashcards

Information System (IS)

A collection of resources used for collecting, managing, controlling, and distributing information within an organization.

Signup and view all the flashcards

Database Security

Ensuring data is protected from unauthorized access and corruption. Involves measures like password security, access rights, and data encryption.

Signup and view all the flashcards

Database Backup and Recovery

The set of procedures used to make sure the data is protected against loss, including backing up the database and testing recovery procedures.

Signup and view all the flashcards

Database Operational Stage

The stage where the database is considered ready for use and the entire system is operational, including data, management, users, and applications.

Signup and view all the flashcards

Database Maintenance

The process of maintaining the database, which includes ensuring its performance, reliability, and security. Tasks may include backups, recovery, and adapting to changes.

Signup and view all the flashcards

Conceptual Database Design

An approach to database design that focuses on understanding and analyzing data requirements from users and the organization. It uses entities, attributes, and relationships to create a model.

Signup and view all the flashcards

Entity-Relationship (E-R) Model

A model that represents the real world as objects (entities), properties of objects (attributes), and connections between objects (relationships).

Signup and view all the flashcards

Enterprise Schema

A data model used for representing the overall structure of a database. It's used to explain how different parts of the database relate to each other.

Signup and view all the flashcards

Multivalued Attribute

An attribute that can hold multiple values for a single entity instance.

Signup and view all the flashcards

Derived Attribute

An attribute whose value can be calculated from other attributes within the entity.

Signup and view all the flashcards

Super Key

A set of attributes that uniquely identify an entity instance within an entity set.

Signup and view all the flashcards

Single-Valued Attribute

An attribute that can hold only one value for a single entity instance.

Signup and view all the flashcards

Composite Attribute

An attribute that is composed of smaller, sub-attributes.

Signup and view all the flashcards

Key

A group of attributes that collectively identify an entity uniquely.

Signup and view all the flashcards

Overlapping Generalization

A type of generalization where an entity can belong to multiple lower-level entity sets within the same generalization.

Signup and view all the flashcards

Participation Constraint

A constraint specifying whether an entity in a higher-level set must belong to at least one lower-level entity set within the specialization or generalization.

Signup and view all the flashcards

Total Generalization or Specialization

Every entity in the higher-level set must belong to a lower-level entity set.

Signup and view all the flashcards

Partial Generalization or Specialization

Some entities in the higher-level set may not belong to any lower-level entity set.

Signup and view all the flashcards

Aggregation

A way to represent relationships as higher-level entity sets.

Signup and view all the flashcards

Relationship between entity and relationship

A relationship between an entity and a relationship that may be needed in certain scenarios.

Signup and view all the flashcards

Double Line in E-R diagram

Used to indicate a total generalization in an E-R diagram, connecting the higher-level entity set to the triangle symbol.

Signup and view all the flashcards

Total vs. Partial Generalization

The completeness constraint for a generalization is usually total, but it can be partial if not all higher-level entities belong to a lower-level entity.

Signup and view all the flashcards

Total Participation

When an entity in a relationship is required to participate, it's called total participation. All instances of that entity must be linked to at least one instance of the related entity.

Signup and view all the flashcards

Partial Participation

If an entity can exist independently from the relationship, it has partial participation. The entity doesn't have to participate in the connection.

Signup and view all the flashcards

Cardinality

Represents the maximum number of relationships an entity can be involved in at any given time. It describes the potential connections an entity can have within the context of a specific relationship type.

Signup and view all the flashcards

Participation

Describes whether all instances of an entity must be involved in a relationship (total participation) or if only some instances have to participate (partial participation).

Signup and view all the flashcards

Strong Entity

An entity that can exist independently and has its own primary key.

Signup and view all the flashcards

Weak Entity

An entity that depends on another entity (its owner) for its existence. It can't exist without the owner entity. Its primary key includes a part of the owner's primary key.

Signup and view all the flashcards

Associative Entity

A special type of entity used to represent a many-to-many relationship between two other entities. Acts as a bridge, connecting two entities with a one-to-many relationship on both ends.

Signup and view all the flashcards

Modeling a Concept: Entity or Attribute?

Addressing a concept as an entity or an attribute depends on the desired use of its information and the meaning behind the data. Example: If a customer can have multiple addresses, address should be an entity. Modeling address as an entity becomes necessary if its structure (Region, Zone, etc.) is crucial for retrieval, as it allows fetching customers within a specific Zone.

Signup and view all the flashcards

Modeling a Concept: Entity or Relationship?

A concept can be modeled as an entity or a relationship based on the need for its unique properties or connections. Example: If a product can be sold at various prices, price should be an entity to show different price options for the same product.

Signup and view all the flashcards

Binary or Ternary Relationships?

A ternary relationship represents an interaction between three entities. Sometimes, a ternary relationship can be better represented with two binary relationships. This choice depends on the specific needs of the database.

Signup and view all the flashcards

Strong vs. Weak Entities

A strong entity is independent and can exist without relying on another, while a weak entity is dependent on another entity for its existence and requires a unique identifier inherited from its strong entity. Example: Order is a strong entity, while Order Item is a weak entity.

Signup and view all the flashcards

Specialization and Generalization

Specialization involves grouping entities into subclasses based on their specific characteristics. Generalization creates a general entity by combining common features from subclasses.

Signup and view all the flashcards

Aggregation in Entity-Relationship Modeling

Aggregation allows treating a group of entities as a single unit, ignoring its internal structure. Example: A 'Car' entity could be aggregated from 'Engine,' 'Body,' and 'Wheels.'

Signup and view all the flashcards

Study Notes

Database Application Development

  • Database Management Systems (DBMS) are crucial for managing and disseminating information within organizations.
  • The Database Development Life Cycle (DBLC) mirrors the System Development Life Cycle (SDLC) for database projects.
  • The SDLC is a structured approach to developing information systems, guiding from planning to final system implementation.

Database Development Life Cycle (DDLC)

  • The DBLC consists of six phases aligning with SDLC principles. These phases are: Database Initial Study, Database Design, Implementation and Loading, Testing and Evaluation, Operation, and Maintenance and Evolution.
  • The phases are:
    • Database Initial Study: Analyze the company's situation (structure, mission, operations); define objectives and scope; collect requirements; and define problems. Requirements gathering methods: interviews, surveys, observations, and examining documents.
    • Database Design: Create a model of data, independent of physical considerations. This encompasses conceptual (overall data model), logical (based on a specific data model like relational) and physical (specific implementation details, storage, and indexes) database design.
    • Implementation and Loading: Involves selecting and installing the DBMS, creating the database(s), and loading the data into the database tables.
    • Testing and Evaluation: Testing the database, integrity, security and performance; implementing backup and recovery plans. Testing and evaluation includes data security, physical security, password security, access rights, and data encryption.
    • Operation: The database becomes fully operational. Its management, users, and application programs constitute the complete information system.
    • Maintenance and Evolution: Routine maintenance, including preventive (backups) and corrective (recovery) maintenance; adjusting performance, adding/modifying entities and attributes ,as well as assigning access permissions.

Conceptual Database Design With E-R Modelling

  • Conceptual Database Design: Focuses on building a model of an enterprise's data, independent of implementation details.
  • Entity-Relationship (E-R) models depict the real world as entities, their attributes, and relationships.
  • Developing an E-R Model:
    • Identify Entities, Attributes, Relationships, and Constraints. These are often nouns, descriptive words/adjectives and verbs respectively.
    • Develop, Validate, Present the Model for Review and Collect Feedback.
  • This iterative process ensures a representation of the organization's activities and functions.

Entity-Relationship (E-R) Diagram Components

  • Entities: Objects or concepts. (e.g.: Customers, Employees, Products, Departments)
  • Attributes: Properties of entities (e.g.: Customer Name, Employee ID, Product Price)
  • Relationships: Links between entities (e.g.: Orders placed by Customers, Products supplied by Suppliers)
  • Cardinality: The maximum number of relationships between entities (e.g.: One-to-One, One-to-Many, Many-to-Many)
  • Participation: Whether all/some entities must participate in a relationship (e.g., Total or Partial).

Attributes

  • Simple Attributes: Attributes that cannot be further subdivided. Examples include sex or social security number.
  • Composite Attributes: Attributes that can be divided into smaller sub-attributes, such as an address with street, city, state, and zip code.
  • Multi-valued Attributes: Allow entities to have more than one value for an attribute, such as phone numbers for a given customer (they can have more than one).
  • Derived Attributes: Attributes that can be calculated from other attributes, such as age from date of birth.

Keys

  • Super Key: A set of attributes that uniquely identifies an entity.
  • Candidate Key: A minimal superkey.
  • Primary Key: A chosen candidate key to uniquely identify an entity occurrence. It is used to identify a unique record in a table.
  • Composite Key: A candidate key composed of more than one attribute.

Relationships

  • Binary Relationships: A relationship involving two entities (e.g., customer placing an order).
  • Ternary Relationships: Involves three entities (e.g., a supplier supplying parts to projects).
  • Degree: The number of entities participating in a relationship (e.g., 2 in binary, 3 in ternary).

Generalization/Specialization

  • Specialization: Defining subtypes (e.g., employee subtype of person, student subtype of person).
  • Generalization: Defining a higher-level entity type from subtypes (e.g., person is the generalization of employee and customer).

Aggregation

  • An abstraction method to represent relationships (entities & relations together) as higher-level entity sets.
  • Helpful when a relationship itself needs to participate in other relationships.

Design Choices

  • Critical decisions during database design including whether attributes or relationships are presented as entities, and the use of binary or ternary relationships.

Constraints of Generalization/Specialization

  • Membership Constraint: Determine which entities can be members of a lower-level entity set.
  • Disjoint Constraint: Specifies that an entity can belong to only one lower-level entity, creating subtypes.
  • Overlap Constraint: Allows an entity to belong to multiple lower-level entities.

Participation Constraint

  • Total Participation: Specifies that every entity in the higher-level entity set is associated with at least one entity in the lower-level entity.
  • Partial Participation: Specifies that some or not all entities are associated with lower-level entities.

Problems with E-R Models

  • Subjectivity of ER Design: Different ways to model the same reality.
  • Capturing Data Semantics: Difficulty in capturing all data semantics completely in ER diagrams.
  • Connection Traps (Fan/Chasm Trap): Ambiguity in relationships when considering entity occurrences might cause difficulties in representing logical relationships between entities.

Studying That Suits You

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

Quiz Team

Related Documents

DBS Chapter Four Part One PDF

Description

Test your knowledge of the Database Development Life Cycle (DBLC) and its phases, including the comparison with the Systems Development Life Cycle (SDLC). This quiz covers key concepts such as the initial study phase, evaluation stage, and the roles of a database administrator. Challenge yourself to match phases with their descriptions and understand the primary goals of these life cycles.

More Like This

Use Quizgecko on...
Browser
Open
Browser
Browser