What is the need for time stamping in modeling time dependent data?
> Explain how referential integrity is established in databases that are SQL:1999 compliant. Explain how the ON UPDATE RESTRICT, ON UPDATE CASCADE, and ON UPDATE SET NULL clauses differ from one another. What happens if the ON DELETE CASCADE clause is set?
> What are the primary data integrity constraints in SQL?
> Define each of the following terms: a. data definition language b. data manipulation language c. referential integrity constraint d. relational DBMS (RDBMS) e. schema
> Demonstrate each of the anomaly types with an example.
> Describe three types of anomalies that can arise in a table and the negative consequences of each.
> What is a schema? Discuss two common methods of expressing a schema.
> List the three components of a relational data model.
> Describe the primary differences between the conceptual and logical data models.
> Consider Figure 1-15. a. What is the purpose of introducing an attribute called Product ID to the Product table? What is its data type? b. If the company wants to keep track of the total outstanding balances of customers, an attribute called â€
> Contrast the following terms: a. normal form; normalization b. candidate key; primary key c. partial dependency; transitive dependency d. composite key; recursive foreign key e. determinant; candidate key f. foreign key; primary key g. natural primary ke
> What are the benefits of the use of an enterprise key?
> Why is the natural key preserved whenever a surrogate key is created?
> Describe the difference between how a 1:M unary relationship and an M:N unary relationship are implemented in a relational data model.
> What is an enterprise key, and why is it important?
> Under what conditions must a foreign key not be null?
> What are the properties that a candidate key must satisfy?
> In the context of unary relationships, what is a recursive foreign key?
> Suggest four steps to represent super/subtype relationships.
> Match the following terms to the appropriate definitions: - well-structured relation - anomaly - functional dependency - determinant - composite key - 1NF - 2NF - 3NF - recursive foreign key - transitive dependency a. constraint between two attributes b.
> Martin is encouraged by the progress you have made so far. As promised, he forwards you an email from one of the key members of his staff, Pat Smith (an artist manager). He also provide you with an e-mail from Shannon Howard, a prospective artist who mig
> How do you represent a 1:M unary relationship in a relational data model?
> What are the benefits of enforcing the integrity constraints as part of the database design and implementation process (instead of doing it in application design)?
> Explain how each of the following types of integrity constraints is enforced in the SQL CREATE TABLE commands: a. entity integrity b. referential integrity
> List the three steps to remove transitive dependencies.
> Discuss how transitive dependencies in a relation can be removed when it leads to anomalies.
> Outline a shortcut to describe relations in 3NF.
> What do you understand by domain constraint?
> Describe how the following components of an E-R diagram are transformed into relations: a. regular entity type b. relationship (1:M) c. relationship (M:N) d. relationship (supertype/subtype) e. multivalued attribute f. weak entity g. composite attribute
> Does normalization place any constraint on the storage of data in physical form or on its processing performance? Explain.
> Define each of the following terms: a. determinant b. functional dependency c. transitive dependency d. recursive foreign key e. normalization f. composite key g. candidate key h. normal form i. partial functional dependency j. enterprise key k. surrogat
> Martin is encouraged by the progress you have made so far. As promised, he forwards you an email from one of the key members of his staff, Pat Smith (an artist manager). He also provide you with an e-mail from Shannon Howard, a prospective artist who mig
> What types of business rules are normally captured in an EER diagram?
> What is a completeness constraint, and what are the total and partial specialization rules?
> What is attribute inheritance? Why is it important?
> Explain how specialization and generalization assist in the development of supertype/subtype relationships.
> Explain the need for EER modeling.
> Discuss the notations used to represent EER models. Which notation is the most widely used?
> Contrast the following terms: a. supertype; subtype b. generalization; specialization c. disjoint rule; overlap rule d. total specialization rule; partial specialization rule e. PARTY; PARTY ROLE f. entity; entity cluster
> Match the following terms and definitions: - supertype - entity cluster - subtype - specialization - subtype discriminator - attribute inheritance - generalization a. subset of supertype b. creating a supertype for entity types c. subtype gets supertype
> When is a member of a supertype always a member of at least one subtype?
> Why must the minimum cardinality next to SUPPLIES from PURCHASED PART be one yet the minimum cardinality next to SUPPLIES from SUPPLIER may be zero?
> Martin is encouraged by the progress you have made so far. As promised, he forwards you an email from one of the key members of his staff, Pat Smith (an artist manager). He also provide you with an e-mail from Shannon Howard, a prospective artist who mig
> Discuss how it is decided which subtype will be inserted with a new instance of a supertype.
> Does a data modeling project using a packaged data model require less or greater skill than a project not using a packaged data model? Why or why not?
> Purchasing a packaged data model involves mapping. What is mapping? What are the points you need to consider in mapping?
> In what ways is starting a data modeling project with a packaged data model different from starting a data modeling project with a clean sheet of paper?
> How are the attributes assigned in a supertype/subtype hierarchy?
> Give an example of generalization not discussed in the text.
> Define each of the following terms: a. supertype b. subtype c. specialization d. entity cluster e. completeness constraint f. enhanced entity-relationship (EER) model g. supertype/subtype hierarchy h. total specialization rule i. generalization j. disjoi
> State the differences between a term and a fact.
> State six general guidelines for naming data objects in a data model.
> Martin is encouraged by the progress you have made so far. As promised, he forwards you an email from one of the key members of his staff, Pat Smith (an artist manager). He also provide you with an e-mail from Shannon Howard, a prospective artist who mig
> What are the characteristics of good business rules?
> Give four reasons why a business rules approach is advocated as a new paradigm for specifying information systems requirements.
> Give four reasons why many system designers believe that data modeling is important and arguably the most important part of the systems development process.
> Contrast the following terms: a. stored attribute; derived attribute b. minimum cardinality; maximum cardinality c. entity type; relationship type d. strong entity type; weak entity type e. degree; cardinality f. required attribute; optional attribute g.
> Why is time stamping considered an important part of the data modeling process?
> Explain any two characteristics of a good business rule.
> For the Manages relationship in Figure 2-12a, describe one or more situations that would result in different cardinalities on the two ends of this unary relationship. Based on your description for this example, do you think it is always clear simply from
> Match the following terms and definitions. - composite attribute - associative entity - unary relationship - weak entity - attribute - entity - relationship type - cardinality constraint - degree - identifier - entity type - ternary - optional attribute
> Why is data modeling considered more important than process modeling?
> What are the special guidelines for naming relationships?
> Interview a DB analyst or systems administrator in your university or at a local company that has adopted a packaged data model. Discuss how they adopted the model. What was the process of customization or mapping involved? Was the process complex? What
> State a rule that says when to extract an attribute from one entity type and place it in a linked entity type.
> Discuss why the E-R model is a popular modeling tool.
> Provide examples (other than those described in this chapter) of multiple relationships, and explain why these examples best represent this type of relationship. Discuss the role of identifiers in modeling this relationship.
> Give an example (other than those described in this chapter) for each of the following, and justify your answer: a. derived attribute b. multivalued attribute c. atomic attribute d. composite attribute e. composite identifier attribute f. optional attrib
> State the guidelines for naming entity types. Discuss why organizations customize a purchased data model.
> The chapter makes a distinction between a required attribute and an optional attribute. Illustrate a required attribute with a relevant example.
> When should an attribute be linked to an entity via a relationship?
> Discuss the main guidelines for defining relationships.
> Define each of the following terms: a. entity type b. entity-relationship model c. entity instance d. attribute e. relationship type f. strong entity type g. multivalued attribute h. associative entity i. cardinality constraint j. weak entity k. binary r
> Explain some of the advantages of large databases that organizations can benefit from considering how the amount of data processed and stored in databases will increase in the future.
> There are other extensions to ER notation than just supertype/subtype relationships. Use the Internet to search for such extensions. One mentioned in the text is aggregation. Look for its examples on the Internet. Report your findings and state the exten
> Why might Pine Valley Furniture Company need a data warehouse?
> Revisit the section titled “Developing a Database Application for Pine Valley Furniture Company.” What phase(s) of the database development process (Figure 1-9) do the activities that Chris performs in the following subsections correspond to: a. Project
> In the three-schema architecture: a. The view of a manager or other type of user is called the schema. b. The view of the data architect or data administrator is called the schema. c. The view of the database administrator is called the schema.
> Explain the differences between user views, a conceptual schema, and an internal schema as different perspectives of the same database.
> Explain why certain business environments favor specific database development methodologies. Highlight the pros and cons of each methodology and the differences in the approaches to database development. Do those differences have any impact on the design
> How does the use of an agile methodology affect decisions regarding data management?
> In which of the five phases of the SDLC do database development activities occur?
> Name the five phases of the traditional systems development life cycle and explain the purpose and deliverables of each phase.
> What differentiates data lakes from traditional data warehouses?
> Specify the difference between database solutions supporting enterprise databases and departmental multitiered databases.
> What is the purpose of designing an enterprise data model? How is it different from the design of a particular database?
> A relationship is established between any pair of entities in an enterprise data model. Explain why a relationship is necessary.
> Figure 1-5 specifies categories for Operational and Informational data management systems. Describe the main difference between these two categories.
> A database is referred to as “an organized collection of logically related data.” What does “related data” mean? Why must data be related?
> List five costs or risks associated with the database approach.
> List 10 potential benefits of the database approach over conventional file systems.
> Table 4-3 contains sample data for parts and for vendors who supply those parts. In discussing these data with users, we find that part numbers (but not descriptions) uniquely identify parts and that vendor names uniquely identify vendors. a. Convert thi
> For your answers to the following Problems and Exercises from prior chapters, transform the EER diagrams into a set of relational schemas, diagram the functional dependencies, and convert all the relations to third normal form: a. Chapter 2, Problem and
> For each of the following relations, indicate the normal form for that relation. If the relation is not in third normal form, decompose it into 3NF relations. Functional dependencies (other than those implied by the primary key) are shown where appropria
> For each of the following EER diagrams from Chapter 3: I. Transform the diagram into a relational schema that shows referential integrity constraints. II. For each relation, diagram the functional dependencies. III. If any of the relations are not in 3NF
> For each of the following E-R diagrams from Chapter 2: I. Transform the diagram to a relational schema that shows referential integrity constraints. II. For each relation, diagram the functional dependencies. III. If any of the relations are not in 3NF,
> Visit your local library and observe the library users and librarians at work. Ask a librarian how the library records and stores its information about its borrowers, books, and loans. Based on this information, determine whether the library’s business r
> What problems may be encountered when developing new programs without designing a database management system?
> Add the following to Figure 3-16: An EMPLOYMENT party relationship is further explained by the positions and assignments to positions during the time a person is employed. A position is defined by an organization unit, and a unit may define many position
> Draw an EER diagram for the following problem: A university is looking to more effectively manage lecture and student appointments. It is currently unable to determine how much time lecturers are devoting to student appointments and consultation and woul
> The description for DocIT explained that there were to be data in the database about people who are not patients but are related to patients. Also, it is possible for some staff members to be patients or to be related to patients. And, some staff members
