Chapter 1 Introduction- review questions icon

Chapter 1 Introduction- review questions


страницы:   1   2   3   4   5


DATABASE SOLUTIONS (2nd Edition)


THOMAS M CONNOLLY & CAROLYN E BEGG


SOLUTIONS TO REVIEW QUESTIONS


Chapter 1 Introduction- Review questions


1.1 List four examples of database systems other than those listed in Section 1.1.

Some examples could be:

  • A system that maintains component part details for a car manufacturer;

  • An advertising company keeping details of all clients and adverts placed with them;

  • A training company keeping course information and participants’ details;

  • An organization maintaining all sales order information.

1.2 Discuss the meaning of each of the following terms:

(a) data

For end users, this constitutes all the different values connected with the various objects/entities that are of concern to them.

(b) database

A shared collection of logically related data (and a description of this data), designed to meet the information needs of an organization.

(c) database management system

A software system that: enables users to define, create, and maintain the database and provides controlled access to this database.

(d) application program

A computer program that interacts with the database by issuing an appropriate request (typically an SQL statement) to the DBMS.

(e) data independence

This is essentially the separation of underlying file structures from the programs that operate on them, also called program-data independence.

(f) views.

A virtual table that does not necessarily exist in the database but is generated by the DBMS from the underlying base tables whenever it’s accessed. These present only a subset of the database that is of particular interest to a user. Views can be customized, for example, field names may change, and they also provide a level of security preventing users from seeing certain data.

^ 1.3 Describe the main characteristics of the database approach.

Focus is now on the data first, and then the applications. The structure of the data is now kept separate from the programs that operate on the data. This is held in the system catalog or data dictionary. Programs can now share data, which is no longer fragmented. There is also a reduction in redundancy, and achievement of program-data independence.

^ 1.4 Describe the five components of the DBMS environment and discuss how they relate to each other.

  1. Hardware: The computer system(s) that the DBMS and the application programs run on. This can range from a single PC, to a single mainframe, to a network of computers.

  2. Software: The DBMS software and the application programs, together with the operating system, including network software if the DBMS is being used over a network.

  3. Data: The data acts as a bridge between the hardware and software components and the human components. As we’ve already said, the database contains both the operational data and the meta-data (the ‘data about data’).

  4. Procedures: The instructions and rules that govern the design and use of the database. This may include instructions on how to log on to the DBMS, make backup copies of the database, and how to handle hardware or software failures.

  5. People: This includes the database designers, database administrators (DBAs), application programmers, and the end-users.

1.5 Describe the problems with the traditional two-tier client-server architecture and discuss how these problems were overcome with the three-tier client-server architecture.

In the mid-1990s, as applications became more complex and potentially could be deployed to hundreds or thousands of end-users, the client side of this architecture gave rise to two problems:

  • A ‘fat’ client, requiring considerable resources on the client’s computer to run effectively (resources include disk space, RAM, and CPU power).

  • A significant client side administration overhead.

By 1995, a new variation of the traditional two-tier client-server model appeared to solve these problems called the three-tier client-server architecture. This new architecture proposed three layers, each potentially running on a different platform:

  1. The user interface layer, which runs on the end-user’s computer (the client).

  2. The business logic and data processing layer. This middle tier runs on a server and is often called the application server. One application server is designed to serve multiple clients.

  3. A DBMS, which stores the data required by the middle tier. This tier may run on a separate server called the database server.

The three-tier design has many advantages over the traditional two-tier design, such as:

  • A ‘thin’ client, which requires less expensive hardware.

  • Simplified application maintenance, as a result of centralizing the business logic for many end-users into a single application server. This eliminates the concerns of software distribution that are problematic in the traditional two-tier client-server architecture.

  • Added modularity, which makes it easier to modify or replace one tier without affecting the other tiers.

  • Easier load balancing, again as a result of separating the core business logic from the database functions. For example, a ^ Transaction Processing Monitor (TPM) can be used to reduce the number of connections to the database server. (A TPM is a program that controls data transfer between clients and servers in order to provide a consistent environment for Online Transaction Processing (OLTP).)

An additional advantage is that the three-tier architecture maps quite naturally to the Web environment, with a Web browser acting as the ‘thin’ client, and a Web server acting as the application server. The three-tier client server architecture is illustrated in Figure 1.4.

^ 1.6 Describe the functions that should be provided by a modern full-scale multi-user DBMS.

Data Storage, Retrieval and Update Authorization Services

A User-Accessible Catalog Support for Data Communication

Transaction Support Integrity Services

Concurrency Control Services Services to Promote Data Independence

Recovery Services Utility Services

1.7 Of the functions described in your answer to Question 1.6, which ones do you think would not be needed in a standalone PC DBMS? Provide justification for your answer.

Concurrency Control Services - only single user.

Authorization Services - only single user, but may be needed if different individuals are to use the DBMS at different times.

Utility Services - limited in scope.

Support for Data Communication - only standalone system.

^ 1.8 Discuss the advantages and disadvantages of DBMSs.

Some advantages of the database approach include control of data redundancy, data consistency, sharing of data, and improved security and integrity. Some disadvantages include complexity, cost, reduced performance, and higher impact of a failure.


Chapter 2 The Relational Model - Review questions

^ 2.1 Discuss each of the following concepts in the context of the relational data model:

(a) relation

A table with columns and rows.

(b) attribute

A named column of a relation.

(c) domain

The set of allowable values for one or more attributes.

(d) tuple

A record of a relation.

(e) relational database.

A collection of normalized tables.

2.2 Discuss the properties of a relational table.

A relational table has the following properties:

  • The table has a name that is distinct from all other tables in the database.

  • Each cell of the table contains exactly one value. (For example, it would be wrong to store several telephone numbers for a single branch in a single cell. In other words, tables don’t contain repeating groups of data. A relational table that satisfies this property is said to be normalized or in first normal form.)

  • Each column has a distinct name.

  • The values of a column are all from the same domain.

  • The order of columns has no significance. In other words, provided a column name is moved along with the column values, we can interchange columns.

  • Each record is distinct; there are no duplicate records.

  • The order of records has no significance, theoretically.

2.3 Discuss the differences between the candidate keys and the primary key of a table. Explain what is meant by a foreign key. How do foreign keys of tables relate to candidate keys? Give examples to illustrate your answer.

The primary key is the candidate key that is selected to identify tuples uniquely within a relation. A foreign key is an attribute or set of attributes within one relation that matches the candidate key of some (possibly the same) relation.

^ 2.4 What does a null represent?

Represents a value for a column that is currently unknown or is not applicable for this record.

    1. Define the two principal integrity rules for the relational model. Discuss why it is desirable to enforce these rules.

Entity integrity In a base table, no column of a primary key can be null.

Referential integrity If a foreign key exists in a table, either the foreign key value must match a candidate key value of some record in its home table or the foreign key value must be wholly null.

Chapter 3 SQL and QBE - Review questions

^ 3.1 What are the two major components of SQL and what function do they serve?

A data definition language (DDL) for defining the database structure.

A data manipulation language (DML) for retrieving and updating data.

3.2 Explain the function of each of the clauses in the SELECT statement. What restrictions are imposed on these clauses?

FROM specifies the table or tables to be used;

^ WHERE filters the rows subject to some condition;

GROUP BY forms groups of rows with the same column value;

HAVING filters the groups subject to some condition;

SELECT specifies which columns are to appear in the output;

ORDER BY specifies the order of the output.

^ 3.3 What restrictions apply to the use of the aggregate functions within the SELECT statement? How do nulls affect the aggregate functions?

An aggregate function can be used only in the SELECT list and in the HAVING clause.


Apart from COUNT(*), each function eliminates nulls first and operates only on the remaining non-null values. COUNT(*) counts all the rows of a table, regardless of whether nulls or duplicate values occur.

^ 3.4 Explain how the GROUP BY clause works. What is the difference between the WHERE and HAVING clauses?

SQL first applies the WHERE clause. Then it conceptually arranges the table based on the grouping column(s). Next, applies the HAVING clause and finally orders the result according to the ORDER BY clause.


WHERE filters rows subject to some condition; HAVING filters groups subject to some condition.

^ 3.5 What is the difference between a subquery and a join? Under what circumstances would you not be able to use a subquery?

With a subquery, the columns specified in the SELECT list are restricted to one table. Thus, cannot use a subquery if the SELECT list contains columns from more than one table.

^ 3.6 What is QBE and what is the relationship between QBE and SQL?

QBE is an alternative, graphical-based, ‘point-and-click’ way of querying the database, which is particularly suited for queries that are not too complex, and can be expressed in terms of a few tables. QBE has acquired the reputation of being one of the easiest ways for non-technical users to obtain information from the database.


QBE queries are converted into their equivalent SQL statements before transmission to the DBMS server.

^ Chapter 4 Database Systems Development Lifecycle - Review questions


    1. Describe what is meant by the term ‘software crisis’.

The past few decades has witnessed the dramatic rise in the number of software applications. Many of these applications proved to be demanding, requiring constant maintenance. This maintenance involved correcting faults, implementing new user requirements, and modifying the software to run on new or upgraded platforms. With so much software around to support, the effort spent on maintenance began to absorb resources at an alarming rate. As a result, many major software projects were late, over budget, and the software produced was unreliable, difficult to maintain, and performed poorly. This led to what has become known as the ‘software crisis’. Although this term was first used in the late 1960s, more than 30 years later, the crisis is still with us. As a result, some people now refer to the software crisis as the ‘software depression’.

    1. ^ Discuss the relationship between the information systems lifecycle and the database system development lifecycle.

An information system is the resources that enable the collection, management, control, and dissemination of data/information throughout a company. The database is a fundamental component of an information system. The lifecycle of an information system is inherently linked to the lifecycle of the database that supports it.


Typically, the stages of the information systems lifecycle include: planning, requirements collection and analysis, design (including database design), prototyping, implementation, testing, conversion, and operational maintenance. As a database is a fundamental component of the larger company-wide information system, the database system development lifecycle is inherently linked with the information systems lifecycle.

    1. ^ Briefly describe the stages of the database system development lifecycle.

See Figure 4.1 Stages of the database system development lifecycle.

Database planning is the management activities that allow the stages of the database system development lifecycle to be realized as efficiently and effectively as possible.


^ System definition involves identifying the scope and boundaries of the database system including its major user views. A user view can represent a job role or business application area.


Requirements collection and analysis is the process of collecting and analyzing information about the company that is to be supported by the database system, and using this information to identify the requirements for the new system.


There are three approaches to dealing with multiple user views, namely the centralized approach, the view integration approach, and a combination of both. The centralized approach involves collating the users’ requirements for different user views into a single list of requirements. A data model representing all the user views is created during the database design stage. The view integration approach involves leaving the users’ requirements for each user view as separate lists of requirements. Data models representing each user view are created and then merged at a later stage of database design.


^ Database design is the process of creating a design that will support the company’s mission statement and mission objectives for the required database. This stage includes the logical and physical design of the database.


The aim of DBMS selection is to select a system that meets the current and future requirements of the company, balanced against costs that include the purchase of the DBMS product and any additional software/hardware, and the costs associated with changeover and training.


^ Application design involves designing the user interface and the application programs that use and process the database. This stage involves two main activities: transaction design and user interface design.


Prototyping involves building a working model of the database system, which allows the designers or users to visualize and evaluate the system.


Implementation is the physical realization of the database and application designs.


^ Data conversion and loading involves transferring any existing data into the new database and converting any existing applications to run on the new database.


Testing is the process of running the database system with the intent of finding errors.


Operational maintenance is the process of monitoring and maintaining the system following installation.

    1. ^ Describe the purpose of creating a mission statement and mission objectives for the required database during the database planning stage.

The mission statement defines the major aims of the database system, while each mission objective identifies a particular task that the database must support.

    1. Discuss what a user view represents when designing a database system.

A user view defines what is required of a database system from the perspective of a particular job (such as Manager or Supervisor) or business application area (such as marketing, personnel, or stock control).

    1. ^ Compare and contrast the centralized approach and view integration approach to managing the design of a database system with multiple user views.

An important activity of the requirements collection and analysis stage is deciding how to deal with the situation where there is more than one user view. There are three approaches to dealing with multiple user views:

  • the centralized approach,

  • the view integration approach, and

  • a combination of both approaches.

Centralized approach

Requirements for each user view are merged into a single list of requirements for the new database system. A logical data model representing all user views is created during the database design stage.


The centralized approach involves collating the requirements for different user views into a single list of requirements. A data model representing all user views is created in the database design stage. A diagram representing the management of user views 1 to 3 using the centralized approach is shown in Figure 4.4. Generally, this approach is preferred when there is a significant overlap in requirements for each user view and the database system is not overly complex.


See Figure 4.4 The centralized approach to managing multiple user views 1 to 3.





Download 261.67 Kb.
leave a comment
Page1/5
Date conversion09.09.2011
Size261.67 Kb.
TypeДокументы, Educational materials
Add document to your blog or website

страницы:   1   2   3   4   5
Be the first user to rate this..
Your rate:
Place this button on your site:
docs.exdat.com

The database is protected by copyright ©exdat 2000-2017
При копировании материала укажите ссылку
send message
Documents

upload
Documents

Рейтинг@Mail.ru
наверх