DATA MODELING AND ANALYSIS TECHNIQUES 1. Data modeling is a technique for defining business requirements for a database.

2. Data modeling is a technique for organizing and documenting a system's logical and physical models.

3. Data modeling is sometimes called database modeling because a data model is eventually implemented as a database.

4.

An entity is something about which the business needs to store data.

5. An entity is a class of persons, places, objects, events or concepts about which we need to capture and store data.

6. An identity is a class of persons, places, objects, events, or concepts about which we need to capture and store data.

7.

An entity instance is a single occurrence of an entity.

8.

An entity existence is a single occurrence of an entity.

9.

An attribute is a descriptive property or characteristic of an entity.

10. A compound attribute is one that actually consists of other attributes that are logically grouped together.

11. A compound attribute is an attribute that will be expanded into a separate entity.

12. The data type of an attribute defines what type of data can be stored in that attribute.

13. Example data types include: numbers, text, memo, date, time, yes/no, Boolean, value set, or image.

14. The domain of an attribute defines what values an attribute can legitimately take on.

15. The domain value for an attribute is the value that will be recorded if not specified by the user.

16. A key is an attribute, or group of attributes, that assumes a unique value for each entity instance. It is sometimes called an identifier.

17. A key is an attribute or group of attributes that assumes a unique value for each entity instance. It is sometimes called the domain of the attribute.

18. A concatenated key is a group of attributes that uniquely identifies an instance of an entity.

19. key.

A concatenated key is also known as a composite key or a compound

20.

A candidate key must be a single attribute.

21.

A candidate key may be a single attribute or a concatenated key.

22. A primary key is that candidate key that will most commonly be used to uniquely identify a single entity instance.

23. An example of domain would be an attribute called grade where the values could only be A, B, C, D, E, or F.

24.

An alternate key is also known as a secondary key.

25.A subsetting criteria is an attribute or concatenated attribute whose finite values divide all entity instances into useful subsets.

26.A subsetting criteria is also known as an inversion entry.

27. A subsetting criteria is a domain of attributes whose values are limitless to allow for a variety of subsets to be constructed from a database.

28. A relationship is a natural business association that exists between one or more entities.

29. A relationship may represent an event that links the entities or merely a physical affinity that exists between the entities.

30.

All data model relationships are unidirectional.

31. Because all relationships are bi-directional in an entity relationship diagram, cardinality must be defined in both directions for every relationship.

32. Conceptually cardinality defines the minimum and maximum attributes that can be added to an entity.

33. The degree of a relationship is the number of entities that participate in the relationship.

34. The domain of a relationship is the number of entities that participate in the relationship.

35. A recursive relationship is when only one entity participates in the relationship.

36. A recursive relationship is a relationship with a degree of infinity, because there is no limit to how many entities participate in the relationship.

37. A recursive relationship identifies a relationship that may exist between different instances of the same entity.

38.

A ternary relationship is a relationship among three entities.

39. The relationship between a student entity and a curriculum entity would be classified as recursive.

40.

In a one-to-many relationship, the parent is the entity on the "one" side.

41. A foreign key in a child entity always matches the primary key in the parent entity.

42. A foreign key in the parent entity always matches the primary key in the child entity.

43. Nonidentifying relationships are those in which each of the participating entities has its own independent primary key. That is, none of the primary key attributes is shared.

44. Nonidentifying relationships are those in which each of the participating entities has dependent primary keys.

45. Identifying relationships are those in which the parent entity contributes its primary key to become part of the primary key of the child entity.

46.

A nonspecific relationship is a many-to-many relationship.

47. A non-specific relationship is one in which many instances of one entity are associated with many instances of another entity.

48. A many-to-many relationship is one in which many entities are associated with other attributes of a different entity.

49.Generalization is a technique wherein the attributes that are common to several types of an entity are grouped into their own entity, called a supertype.

50. Generalization is a technique wherein the domains common to several types of attributes are grouped into their own entity, called an associate entity.

51. An entity subtype is an entity whose instances inherit some common attributes from an entity supertype and then add other attributes that are unique to an instance of the subtype.

52. An entity supertype is an entity whose instances inherit some common attributes from an entity subtype and then add other attributes that are unique to an instance of the supertype.

53. An enterprise data model typically identifies only the most fundamental of entities of the enterprise.

54. An enterprise data model typically identifies and defines only the most complex entities used by the enterprise.

55. The data model for a single information system is usually called an application data model.

56. The context data model is prepared during the problem analysis phase and only includes entities and relationships, but no attributes.

57. The requirements analysis results in a logical data model that is developed in stages as follows: (1) context data model; (2) key-based data model; (3) fully attributed data model; and (4) the normalized data model.

58. The requirements analysis results in a physical data model that is developed in stages as follows: (1) normalized data model; (2) key-based data model; (3) fully attributed data model; and (4) the context data model.

59. During systems design, the logical data model will be transformed into a physical data model.

60. During the requirements phase, the physical data model is transformed into the logical data model.