






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Database Systems: Design, Implementation, and Management: Chapter 1
Typology: Exams
1 / 10
This page cannot be seen from the preview
Don't miss anything!







1 /
Field: an attribute, same data type Record: related data that describes an entity File: a collection of related records.
same data are stored in multiple places unnecessarily. The use of spreadsheets and tables in ditterent parts of the organization can cause it.
characteristics without impeding the program's ability to access the data.
a collection of programs that manages the database structure and controls access to the data stored in the database. (think electronic filing cabinet) functions of a DBMS:
2 / data dictionary management data storage management data transformation and presentation security management multi user access control backup and recovery management data integrity management database access languages and application programming interfaces. database communication interfaces.
affecting the application program's ability to access the data.
data that has been processed and given context. Databases help to facilitate the manipulation of data to create information by providing an organizational structure that makes relationships and connections between data explicit.
between the user and the database. advantages: improved data sharing improved data security better data integration minimized data inconsistency improved data access improved decision making
4 /
people procedures data
decision making -- and bad decision making can lead to the failure of an organization.
trained personnel
prevalent in a typical business environment?: unstructured data is simply data that has not been processed to yield information. examples of both types would include:
5 / An invoice. If one were to take an invoice and simply scan it into a graphic, it would be unstructured data. In contrast, if it were processed and put into a database (subsequently becoming structured data), employees could eventually find the monthly averages, amount owed, etc. from various invoices. While both are prevalent, I would think semi-structured data would be the most common in a typical business. Some data is stored but not processed (unstructured data such as memos), and some others are stored in databases (such as invoices) but most data are only processed to a certain extent that is displayed in a prearranged format but not able to yield all of the information contained within.
support basic functionality such as: support for self-documentation through metadata enforcement of data types or domains to ensure consistency of data within a column, defined relationships among tables, or contraints to ensure consistency of data across related tables.
system?: Common problems with using both a collection of spreadsheets created by end users and the typical file system include: lengthy development times difficulty of getting quick answers complex system administration lack of security and limited data sharing extensive programming
experienced with the advent of computerized data repositories: The loss of direct, hands on access to business data to end-users was significant because it gave them the tools to convert their data into the information they needed and manipulating the company data that would allow them to create new information.
7 /
embodies both data and behavior. That is, the object contains, in addition to data, also the description of the operations that may be performed by the object.
8 /
a specific class. It is useful to point out that the object is a run-time concept, while the class is a more static description. Objects that share similar characteristics are grouped in classes. A class is a collection of similar objects with shared structure (attributes) and behavior (methods.) Therefore, a class resembles an entity set. However, a class also includes a set of procedures known as methods.
entities. Three types of relationships exist: one-to-one (1:1), one-to-many (1:M), and many-to-many (M:N or M:M.)
These relations are based on algebraic set theory. However, the user perceives the relations to be tables. In the relational database environment, designers and users perceive a table to be a matrix consisting of a series of row/column intersections.Tables, also called relations, are related to each other by sharing a common entity characteristic. For example, an INVOICE table would contain a customer number that points to that same number in the CUSTOMER table. This feature enables the RDBMS to link invoices to the customers who generated them. Tables are especially useful from the modeling and implementation perspectives. Because tables are used to describe the entities they represent, they provide an easy way to summarize entity characteristics and relationships among entities. And, because they are purely conceptual constructs, the designer does not need to be concerned about the physical implementation aspects of the database design.
the attributes within those entities, and the relationships between those entities. Therefore, it is easy to see what the entities represent and to see what types of relationships (1:1, 1:M, M:N) exist among the entities and how those relationships are implemented.
passive verb
business insight from it, while simultaneously providing high performance and scalability at a reasonable cost.
10 /
Entity integrity is important because it means that a proper search for an existing tuple will always be successful and the failure to find a match on a row search will always mean that the row for which the search is conducted does not exist in that table. Referential integrity is important because its existence ensure that it will be impossible to assign a non existing foreign key value to a table. For example, the referential integrity enforcement in a SALESREP is assigned to CUSTOMER relationship means that it will be possible for a customer to not have a sales rep assigned to him or her but it will be impossible to assign non existing sales rep to a customer.
relational terminology, the statement may be translated to " the table or entity set contains two hundred rows/tuples.
Project, Divide, Product, and Join
relating to the datatypes used and sizes as well has the relations in the database.
nine fields." Use appropriate relational database termi- nology to "translate" that statement.: An entity set contains two hundred tuples with each record consisting of nine attributes.
primary key partially or totally derived from the parent entity in the relationship
is when an entity is existence-dependent on another entity and inherits at least part of its primary key from that entity
relationships. A composite entity, also known as a bridge entity, is one that has a primary key composed of multiple attributes. The PK attributes are inherited from the entities that it relates to one another.