Scribd Logo
Upload

Welcome to Scribd!

  • 2K views

    Consider The ER Diagram Shown in Figure 7

    Uploaded by

    M.M Hussain
    The document describes an ER diagram for part of a BANK database. It includes entity types such as Bank, Branch, Account, Loan, and Customer. Branch is a weak entity type whose partial key is Branch No. and identifying relationship is Branches. The question asks to list entity types, identify the weak entity, describe constraints of the partial key and identifying relationship, list relationship types and their cardinalities, summarize user requirements, and describe how updated constraints would appear in the diagram.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Consider The ER Diagram Shown in Figure 7

    Uploaded by

    M.M Hussain
    2K views2 pages
    The document describes an ER diagram for part of a BANK database. It includes entity types such as Bank, Branch, Account, Loan, and Customer. Branch is a weak entity type whose partial key is Branch No. and identifying relationship is Branches. The question asks to list entity types, identify the weak entity, describe constraints of the partial key and identifying relationship, list relationship types and their cardinalities, summarize user requirements, and describe how updated constraints would appear in the diagram.

    Original Title

    Consider the ER diagram shown in Figure 7.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes an ER diagram for part of a BANK database. It includes entity types such as Bank, Branch, Account, Loan, and Customer. Branch is a weak entity type whose partial key is Branch No. and identifying relationship is Branches. The question asks to list entity types, identify the weak entity, describe constraints of the partial key and identifying relationship, list relationship types and their cardinalities, summarize user requirements, and describe how updated constraints would appear in the diagram.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    2K views2 pages

    Consider The ER Diagram Shown in Figure 7

    Uploaded by

    M.M Hussain
    The document describes an ER diagram for part of a BANK database. It includes entity types such as Bank, Branch, Account, Loan, and Customer. Branch is a weak entity type whose partial key is Branch No. and identifying relationship is Branches. The question asks to list entity types, identify the weak entity, describe constraints of the partial key and identifying relationship, list relationship types and their cardinalities, summarize user requirements, and describe how updated constraints would appear in the diagram.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 2

    Consider the ER diagram shown in Figure 7.21 for part of a BANK database.

    Each bank can have multiple branches, and each branch can have multiple
    accounts and loans.
    a. List the strong (non weak) entity types in the ER diagram.
    b. Is there a weak entity type? If so, give its name, partial key, and identifying
    relationship.
    c. What constraints do the partial key and the identifying relationship of the
    weak entity type specifies in this diagram?
    d. List the names of all relationship types, and specify the (min, max) constraint
    on each participation of an entity type in a relationship type.
    Justify your choices.
    e. List concisely the user requirements that led to this ER schema design.
    f. Suppose that every customer must have at least one account but is
    restricted to at most two loans at a time, and that a bank branch cannot
    have more than 1,000 loans. How does this show up on the (min, max)
    constraints?
    Answer: -

    (a) Entity Types: Bank, Account, Customer, Loan.


    (b) Weak Entity Type: Bank-Branch.
    Partial Key: Branch No.
    Identifying Relationship: Branches.
    (c) The Partial Key Branch No. in Bank-Branch specifies that the
    same Branch No. value occur under different Banks. The
    identifying relationship Branches specifies that Branch No.
    values are uniquely assigned for those Bank-Branch entities that
    are related to the same Bank entity. Hence the combination of
    Bank Code and Branch No. together constitute a full identifier
    for a Bank-Branch.
    (d) Relationship Types: Branches, Accts, Loans, A-C, L-C. The
    (min, max) constraints are shown below.
    (e) The requirement may be started as follow: Each Bank has a
    unique code, as well as a Name and Address. Each Bank is
    related to one or more Bank-Branches, and the Branch No. is
    unique among each set of Bank-Branches that are related to the
    same Bank. Each Bank-Branch has an address. Each Bank-
    Branch has zero or more Loans and zero or more ACCTS. Each
    Account has an Acct No. (unique). Balance and type and are
    related to exactly one Bank-Branch and to at least one
    Customer. Each Loan has a Loan No. (unique). Amount and
    type and are related to exactly one Bank-Branch and to at least
    one Customer. Each Customer has an SSN (unique), Name,
    Phone. and Address, and is related to zero or more Account and
    zero to more Loans.
    (f) The (min, max) constraints would be changed as follow

    You might also like