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 might use FAME’s services. E-mail from Pat Smith, Artist Manage I am Pat Smith, and I am one of the 20 artist managers working for Mr. Forondo. I have worked for him for 15 years, and I am one of the most senior managers within the company. I enjoy working here because Mr. Forondo trusts me and knows that I will do my job. One area we have been lacking in during the last 10–15 years is the use of computers to support our jobs, and it is great to hear and notice that something is happening in this area. There are two areas that I find particularly important for me. First, I would like to have a system that would help me track prospective artists. There are so many talented musicians around the world that it is almost impossible to know who is doing what and where without keeping very good records and it seems that this would be an area where computers really could help. There are a lot of sources from which I get hints about young artists whose career I should start to follow. Sometimes my friends who are music critics call me and recommend a particular young artist they have heard; sometimes I myself hear a promising artist perform; sometimes we find a jewel among the unsolicited recordings that are sent or referred to us; and we also follow a large number of newspapers, magazines, and websites that review performances. Over the years we have earned to value the opinions of certain critics who write reviews, thus it is very important to know the source of a recommendation or an opinion. Sometimes I deal with dozens or even hundreds of recommendations per day and thus the lists that I maintain in a Word file on my laptop just are not very easy to use and organize. The system for managing prospective artists should keep track of the artists (including their name, gender, year of birth, instrument(s), university degrees, address, phone number, e-mail, honors, etc.) and all the situations in which we have heard of them (including the source, a brief summary, a brief quality evaluation, and space for storing the original story or a reference to it if it was a review either in a newspaper or on the Web). It is essential that I can get this data reported quickly and in an easy-to-read format. It would be fantastic if I could query the database from my personal tablet and smartphone; I definitely need access to my laptop while on the road. This info would be maintained by any of the managers in the company or their administrative assistants (the assistants take care of most of the work with the reviews). I don’t know if Mr. Forondo told you but he makes the final decisions regarding who becomes the artist manager for a new artist if there is any question about the contributions in recruiting the artist. The second system I would find very helpful would be an application that reports the revenues my artists have earned in the past (we should be able to choose the period freely) and are predicted to earn in the future based on the contracts we have signed for them with our clients. This way, I would know how much I am earning and going to earn in the future. Somehow, it would be great if the system could also tell how much money I have spent on travel; as you might have learned, we managers pay our own travel costs from the 60 percent of royalties we receive. I am really happy we don’t need to pay the assistant’s salaries, too. E-mail from Shannon Howard, Prospective Artist I am Shannon Howard, a soprano from Bloomington, Indiana, and I have had some initial discussions with Pat Smith at FAME regarding the possibility that they might take me under management. I feel that having a good manager would be very important for my career, and I believe that FAME would provide excellent service for me. One area where FAME is not yet very strong is marketing their artists on the Internet, and maybe your project could have some impact in this area. I think it would be an excellent idea if prospective concert organizers could see an artist’s information on the Web and also hear samples of his/her music. In addition, information about an artist’s availability should be available on the Internet. By the way, has anybody remembered to tell you that an artist may be prevented from performing somewhere not only because of an earlier commitment to perform but also because of rehearsals or time needed for travel? Sometimes large productions need long practice times and transcontinental travel also can take several days away from an artist’s schedule. For me it is very important that I can personally negotiate with my manager what I will perform and what I won’t, and I think it would be great if my manager would know what repertoire I have already prepared and what I am not willing or able to perform at this time. Also, it would be great if I could block time away from my calendar in different priority groups so that I could say that certain days I am definitely not available, certain days are not very good but I can perform if Pat can find an excellent opportunity for me, and on certain days I can take any work. I don’t know if this is realistic technologically and whether or not Pat would accept the idea, but it sure would be nice from my perspective. The smoother all types of practical issues go, the better I can focus on my actual work, i.e., singing. Therefore, I feel that it is very important that FAME has a good computer system to help them in their work for me (assuming I can sign up with them—wish me luck!). I would find it very helpful if they could tell me at the end of the year how much money I have made and from whom I received it—it won’t be a long list in the beginning but hopefully it will become much more extensive over time. I don’t know if you have thought about it but just in case I have gigs around the world it would be very nice if the system could also tell how much (if anything) each of the governments withheld from my pay at the source before it was forwarded to FAME and if the payments could be sorted and subtotaled by country. If you wonder what this could mean in practice, let me give you an example. Let’s say I am performing in Finland and Finland has an at-the-source tax for artists of 15 percent. If my fee there is $2,000, my employer in Finland has to withdraw 15 percent of my fee and pay it to the Finnish government; therefore, FAME will receive only $1,700, and if their royalty is 30 percent, I will receive only $1,190. At the end of the year, FAME should give me a report including four columns: my original fee (i.e., $2,000 in this case), tax-at-source ($300), FAME’s share ($510), and finally my share ($1,190). The math is simple but it is essential that this is done correctly so that I won’t be in trouble with the tax authorities either in foreign countries or here in the United States. Project Questions: Use the narratives in Chapter 1 and above to identify the typical outputs (reports and displays) the various stakeholders might want to retrieve from your database. Now, revisit the EER diagram to ensure that your model has captured the information necessary to generate the outputs desired. Update your EER diagram as necessary.
> SQL:2006 and SQL:2008 introduced a new key word, MERGE. Explain how using this key word allows one to accomplish updating and merging data into a table using one command rather than two.
> What is an identity column? Explain the benefits of using the identity column capability in SQL.
> What considerations should be kept in mind when using indexing?
> Explain why SQL is called a set-oriented language.
> Investigate whether the organization follows more of a traditional file processing approach or the database approach to organizing data. How many different databases does the organization have? Try to draw a figure, similar to Figure 1-2, to depict some
> Contrast transactional and analytical data management approaches.
> How do you determine the order in which the rows in a response to an SQL query appear? What options do you have when specifying this order?
> In what clause of a SELECT statement is an IN operator used? What follows the IN operator? What other SQL operator can sometimes be used to perform the same operation as the IN operator? Under what circumstances can this other operator be used?
> How is the HAVING clause different from the WHERE clause?
> Match the following terms to the appropriate definitions: - referential integrity constraint - SQL: 2016 - Null value - scalar aggregate - vector aggregate - catalog - schema - host language a. list of values b. description of a database c. missing or no
> If an SQL statement includes a GROUP BY clause, the attributes that can be requested in the SELECT statement will be limited. Explain that limitation.
> What is the evaluation order for the Boolean operators (AND, OR, NOT) in an SQL command? How can a query writer be sure that the operators will work in a specific, desired order?
> What is the difference between COUNT, COUNT DISTINCT, and COUNT(*) in SQL? When will these three commands generate the same and different results?
> How is the order in which attributes appear in a result table determined? How are the column heading labels in a result table changed?
> Explain and provide at least one example of how to qualify the ownership of a table in SQL. What has to occur for one user to be allowed to use a table in a database owned by another user?
> Explain the factors to be considered in deciding whether to create an index for a column in SQL.
> In this chapter, we described four important data models and their properties: enterprise, conceptual, logical, and physical. In the following table, summarize the important properties of these data models by entering a Y (for yes) or an N (for no) in ea
> What are the potential consequences of inappropriate indexing decisions?
> Explain the purpose of indexing in database implementation.
> 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
> 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
> What is the need for time stamping in modeling time dependent data?
> 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?