Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key


Play button


Play button




Click to flip

45 Cards in this Set

  • Front
  • Back
Rule that can't be violated by database user
Data that describe properties of end-user data and the context of that data
Centralized knowledge base of all data definitions, relationships, screen and report formats, and other system components
Person,place,object,event, or concept in the user environment grouped into a single abstract entity type.
Data Independence
Separation of data descriptions from the application programs that use the data
Conceptual Scheme
Detailed, technology-independent specification of the overall structure of organizational data.
Logical Data model
Representation of a database for a particular data management technology.
Iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analyst and users.
System Development life cycle vs prototyping
Used to develop, maintain, and replace information systems vs. requirements that are continually revised through close work between analyst and users.
Internal Scheme
Consists of logical scheme and physical scheme. Logical is representation of data for a type of data management technology while physical scheme describes how data are to be represented and stored in secondary storage.
Data vs. Information
Data - stored representations of objects and events that have meaning and importance in the users environment.

Data that have been processed in such a way as to increase the knowledge of the person who uses the data.
Repository vs. Database
Repository - centralize knowledgebase of all data definitions, data relationships, screen and report formats,

Database - Organized collection of logically related data.
Data dependence vs. independence
Data independence - separation of data descriptions from the application programs that use the data

Data dependence - no seperation
5 major components in database system.
CASE tools
Application Programs
User interface
Data and database administrators
System developers
End users
What are client, application, and enterprise tiers
Client tier - desktop or laptop computer which concentrates on managing the user-system interface and localized data

Application tier- Processes HTTP protocol, scripting tasks, performs calculations, and provides access to data

Enterprise tier - Performs sophisticated calculations and manages the merging of data from multiple sources across the organization.
Internal Scheme vs. conceptual scheme
Internal schema is the end result, conceptual scheme is view of data architect or data administrator.
Information Engineering and the difference between it and systems development life cycle
Info Engineering - emphasizes the importance of understanding relevant data when creating and maintaining information systems.

System development life cycle - Used to develop, maintain, and replace information systems
Property or characteristic of an entity type that is of interest to the org.
Derived attribute
Attribute whose values can be calculated from related attribute values.
Number of instances of one entity that can be associated with each instance of another entity
Binary relationship
Relationship between the instances of 2 entities
Entity-relationship model(E-R model)
Logical representation of the data for an organization or for a business area.
Multivalued attribute
May take on more than one value for a given entity instance.
Entity Instance
Single occurance of an entity type.
Strong entity vs. weak entity
Strong - exists independently of other entity types.
Weak - existence depends on some other entity
Entity type vs. relationship type
Entity type - Collection of entities that share common properties.
Relationship type - meaningful association between entity type.s
Business Rule
Statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control the behavior of the business.
Subgrouping of entities in an entity type that is meaningful to the organization and that shares common attributes distinct from other subgroupings
Generic entity that has a relationship with one or more subtypes.
Action assertions
Statement of constraint or control on the actions of the organization.
Completeness constraint
Type of constraint that address the question whether an instance of a supertype must also be a member of at least one subtype.
What is attribute inheritance?
Property by which subtype entities inherit values of all attributes of the super type.
Named 2d table of data
Primary Key
Attribute or combination of attributes that uniquely identifies each row in a relation.
Data Integrity
built into the physical structure of the fields and controls enforced by the DBMS on those fields.
Referential Integrity
Integrity constraint specifying that the value of an attribute in one relation depends on the value of a primary key in the same or another relation.
Process of decomposing relations with anonmalies to produce smaller; well-structured relations.
Candidate Key
Attribute or combination of attributes that uniquely identifies a row in a relation.
Two or more attributes having different names but the same meaning, as when they describe the same characteristic of an entity.
Transitive dependency
Functional dependency between two or more non-key attributes.
Attribute on the left-hand side of the arrow in a functional dependency.
Recursive foreign key
Foreign key in a relation that references the primary key values of that same relation.
Partial dependency vs transitive dependency
Partial - one or more attributes dependent on part but not all of primary key
Transitive - two or more non-key attributes are dependent on each other.
Foreign key vs. primary key
Foreign - serves as the primary key of another relation in the same database
Primary - Uniquely identifies each row in a relation.
Normal form vs. normalization
Normal form - state of a relation that results from applying simple rules regarding functional dependencies to that relation.
Normalization - Process of decomposing relations with anomalies to produce smaller, well-structured relations.