MIS 372 - Ch. 3

Card Set Information

Author:
julie_durst
ID:
37147
Filename:
MIS 372 - Ch. 3
Updated:
2010-10-04 02:53:36
Tags:
MIS Modern Database Management 9th Edition
Folders:

Description:
MIS Modern Database Management - 9th Edition
Show Answers:

Home > Flashcards > Print Preview

The flashcards below were created by user julie_durst on FreezingBlue Flashcards. What would you like to do?


  1. What is a business rule?
    A statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business.
  2. What is the job of a Database Analyst?
    • Identify and understand those rules that govern data.
    • Represent those rules so that they can be unambiguously understood by information systems developers and users.
    • Implement thos rules in database technology.
  3. Define "term"
    A word or phrase that has a specific meaning for the business.
  4. Define "fact"
    An association between two or more terms.
  5. When should a data object be added to a data model?
    Not until it has been carefully defined and named and there is agreement on this definition.
  6. What is an Entity-Relationship model?
    A logical representation of the data for an organization or for a business area using entities for categories of data and relationships for associations between entities.
  7. What is an entity-relationship diagram?
    A graphical representation of an entity-relationship model.
  8. Define "Entity"
    A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data.
  9. Define "entity type"
    A collection of entities that share common properties or characteristics.
  10. Define "entity instance"
    A single occurrence of an entity type.
  11. Define "strong entity type"
    An entity that exists independently of other entity types.

    Examples include STUDENT, EMPLOYEE, AUTOMOBILE, and COURSE.
  12. Define "weak entity type"
    An entity type whose existence depends on some other entity type.
  13. Define "identifying owner (owner)"
    The entity type on which the weak entity type depends.
  14. Define "identifying relationship"
    The relationship between a weak entity type and its owner.
  15. Define "attribute"
    A property or characteristic of an entity or relationship type that is of interest to the organization.
  16. Define "required attribute"
    An attribute that must have a value for every entity (or relationship) instance with which it is associated.
  17. Define "Optional Attribute"
    An attribute that may not have a value for every entity (or relationship) instance with which it is associated.
  18. Define "Composite attribute"
    An attribute that has meaningful component parts (attributes).
  19. Define "Simple (or atomic) attribute"
    An attribute that cannot be broken down into smaller components that are meaningful to the organization.
  20. Define "Multivalued attribute"
    An attribute that may take on more than one value for a given entity (or relationship) instance.
  21. Define "Derived attribute"
    An attribute whose values can be calculated from related attribute values.
  22. Define "Identifier"
    An attribute (or combination of attributes) whose value distinguishes instances of an entity type.
  23. Define "Composite Identifier"
    An identifier that consists of a composite attribute.
  24. Define "Relationship Type"
    A meaningful association between (or among) entity types.
  25. Define "Relationship instance"
    An association between (or among) entity instances where each relationship instance associates exactly one entity instance from each participating entity type.
  26. Define "Associative entity"
    An entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances.
  27. Define "Degree"
    The number of entity types that participate in a relationship.
  28. Define "Unary Relationship"
    A relationship between instances of a single entity type.
  29. Define "Binary Relationship"
    A relationship between the instances of two entity types.
  30. Define "Ternary Relationship"
    A simulataneous relationship among the instances of three entity types.
  31. Define "Cardinality Constraint"
    "Specifies the number of instances of one entity that can (or must) be associated with each instance of another entity.
  32. Define "Minimum Cardinality"
    The minimum number of instances of one entity that may be associated with each instance of another entity.
  33. Define "Maximum Cardinality"
    The maximum number of instances of one entity that may be associated with each instance of another entity.
  34. Define "Time Stamp"
    A time value that is associated with a data value, often indicating when some event occurred that affected the data value.

What would you like to do?

Home > Flashcards > Print Preview