chapter 3
involves creating working model that need not necessarily have all the features that the final product will have. One of the main reasons to create working model is to allow individuals to test the system, to identify features that work well and features that may need more work, or to suggest needed features that may have been left out of the original design phase A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
B) Create database application prototypes
All components of the user interface should be employed at this stage, including menus, data entry forms, report generating programs, and user logon screens. Security considerations should have already been outlined and should be applied at this point. Some of these security features are effected using the DCL, but also may be executed using the DBMS or the host platform for the database and its application A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
C) Implement database application
For the database, this will typically include executing DDL statements to create the tables of the database. Any views that have been defined are usually created at this point as well. A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
C) Implement database application
The application programs are executed in the designated programming language. Usually, the application programs contain DML statements embedded within a specific programming language such as C, C++, Java, or Visual Basic. A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
C) Implement database application
This phase includes executing the necessary programming constructs to create the database and its application. This phase can occur with or without the aforementioned prototyping, but will usually run more smoothly if the prototyping occurs. A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
C) Implement database application
Before you create a database, information pertinent to the database must be gathered. The business plans and goals of the organization must be documented. This step will help the database designer to determine the needs that the database will be designed to meet. A) Create a database strategy B) Define the scope of the database application C) Create a database requirements document D) Design the database
Create a database strategy
Current information systems need to be analyzed. The goal of this step is two fold. First, it can help determine the type of data that the database will be handling. Second, any existing strengths of the current system can be noted and used in the subsequent database design effort. A) Create a database strategy B) Define the scope of the database application C) Create a database requirements document D) Design the database
Create a database strategy
One common activity during this phase of database planning is the creation of a corporate data model. This data model can be used to show important data, any relationships among the data, and how that data is associated with key functional units throughout the organization. A) Create a database strategy B) Define the scope of the database application C) Create a database requirements document D) Design the database
Create a database strategy
The loading of old data is only necessary if the database system is replacing an old system. Many database management systems include functionality that helps convert legacy data into the new format. A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
D) Convert legacy data and load new data into the database
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Data dictionary A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Data integrity mechanisms A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Data model type A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Data types supported A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Domain support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Enforcement of primary keys A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Foreign key support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Schema support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Support for views A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Data definition functionality
This step involves designating the boundaries of the database application and how it may interface with other parts of the organization's Information Technology (IT) infrastructure. This activity involves defining the users of the database and its corresponding application. This step should also take into account any possible future users of the database, as well as identify the major areas of the database application. A) Create a database strategy B) scope of the database application C) Create a database requirements document D) Design the database
Define the scope of the database application
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: CASE tool availability A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Development tools
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Fourth- or fifth-generation language tools A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Development tools
TRUE / FALSE A requirements document can contain the following types of information: Other issues may be included, such as security, reliability, maintainability. while portability, and extensibility is mentioned only during the Convert legacy data phase along with the preliminary schedule and a preliminary budget.
FALSE Other issues may be included, such as security, reliability, maintainability, portability, and extensibility. Optionally, a preliminary schedule and a preliminary budget.
TRUE / FALSE A requirements document can contain the following types of information: A set of entities and attributes for the database system from the user's perspective. The document may include a wish list of desirable characteristics, along with more feasible solutions that are in accordance with the organization's business objectives
False A set of objectives and requirements for the database system from the user's perspective. The document may include a wish list of desirable characteristics, along with more feasible solutions that are in accordance with the organization's business objectives.
A database requirements document contains the specifications for the database. Information is gathered for each major user view (that is, job role or enterprise application area), including select all that applies A) a description of the data used or generated B) list of all domains, attributes, entities and their relationships C) the details of how data is to be used or generated D) any additional requirements for the new database system E) different user views and constraints
Information is gathered for each major user view (that is, job role or enterprise application area), including: a description of the data used or generated; the details of how data is to be used or generated; any additional requirements for the new database system.
is creating database __ contains the specifications for the database. It includes information about the required features of the database. A) system catalog B) database definition C) requirements document D) system definition
A database requirements document contains the specifications for the database. It includes information about the required features of the database.
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Interface capabilities with other systems A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Access criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Interface capabilities with programming languages A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Access criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Multiuser capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Access criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Query language (SQL) support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Access criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Security capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Access criteria
This phase actually happens in two places: before the implementation of the database system, and after the system goes live. This is performed to locate and fix errors that may be present in both the database and the database's application. This should be performed with carefully designed testing strategies with real data so that the entire system is thoroughly during this step A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
Test the database and database application This phase actually happens in two places: before the implementation of the database system, and after the system goes live. Testing is performed to locate and fix errors that may be present in both the database and the database's application
The database design phase usually occurs in three stages: ___. Later lessons will examine the methodologies concerned with the database design phase because this phase is the focus of this class. select all that applies: A) methodologies B) conceptual C) normalization D) logical E) physical
The database design phase usually occurs in three stages: conceptual, logical, and physical design. Later lessons will examine the methodologies concerned with the database design phase because this phase is the focus of this class. chapter 4 conceptual chapter 5 normalization chapter 6 logical chapter 7 physical
in the database design life cycle. The functionality required by the user must be built into the database application. In addition, an appropriate interface must be planed. The interface is obviously one of the most important components of the system. If it is well planed, easy to use, and easy to learn, the users will be inclined to use the system A) Design the database application B) Create database application prototypes C) Implement database application D) Convert legacy data and load new data into the database E) Test the database application
The functionality required by the user must be built into the database application. In addition, an appropriate interface must be designed. The interface is obviously one of the most important components of the system. If it is well designed, easy to use, and easy to learn, the users will be inclined to use the system Design the database application
The information for the requirements document can be gathered in several different ways, including: select all that applies A) interviewing principal individuals B) web research from other database design specialist C) using information gleaned from surveys D) analysis of the current database
The information for the requirements document can be gathered in several different ways, including interviewing principal individuals within the organization, using information gleaned from surveys of a wide range of potential users, and using the results of the analysis of the current database.
of the data base design life cycle involves the selection of a DBMS that is appropriate for the database system A) Evaluate and shortlist two or three products B) Recommend selection and produce a report C) Define Terms of Reference of Study D) list system and performance requirements, security, integrity, and constraints
The main steps to selecting a DBMS are as follows: Define Terms of Reference of Study. Shortlist two or three products. Evaluate products. Recommend selection and produce a report.
is the actual designing of the database. The database's design must support the needs of the organization. The information gathered in the preceding steps is used to ensure that these goals are met. The objectives of the database design stage are to present a data: select all that applies A) create a design that is structured to achieve the specified goals B) designate the data and the data relationships required C) present a data model that delineates the transactions required D) present the ER model to all users
The objectives of the database design stage are: To designate the data and the data relationships required by the users To present a data model that delineates the transactions required on the data To create a design that is structured to achieve the specified performance goals of the database system
is the actual designing of the database. The two main approaches to the design of a database. The __ approach starts with the development of data models that contain a few high-level entities and relationships and then apply successive refinements to identify lower-level entities, relationships, and associated attributes. A) top-down B) top-bottom C) bottom-up D) down-up
The top-down approach starts with the development of data models that contain a few high-level entities and relationships and then apply successive top-down refinements to identify lower-level entities, relationships, and associated attributes.
is the actual designing of the database. The two main approaches to the design of a database. The __ approach begins at the fundamental level of attributes (that is, properties of entities and relationships), which through analysis of the associations between attributes are grouped into relations that represent types of entities and relationships between entities A) top-down B) top-bottom C) bottom-up D) down-up
The two main approaches to the design of a database are referred to as "bottom-up" and "top-down." The bottom-up approach begins at the fundamental level of attributes (that is, properties of entities and relationships), which through analysis of the associations between attributes are grouped into relations that represent types of entities and relationships between entities.
Someone other than the database designer or developer should test the database and the application accessing the database. This process is referred to as ___. Someone conducting this type of testing has direct access to the code and may be authorized to make changes to the code. Certainly, a glass-box tester should understand the code, and be able to suggest changes A) Glass- box B) Clear- box C) White- box D) Dark-box E) Black- box
This process is referred to as "glass-box" or "white-box" testing. Someone conducting this type of testing has direct access to the code and may be authorized to make changes to the code. Certainly, a glass-box tester should understand the code, and be able to suggest changes
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Advanced transaction capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Backup and recovery capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Concurrency control A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Logging system A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Rollback and commit ;support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Support for stored procedures A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Transaction speed A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Transactions
TRUE / FALSE A requirements document can contain the following types of information: Possible constraints placed on the database designer, including speed requirements, hardware platforms, and so on. A description of the graphical user interface (GUI). If the GUI is menu-driven, a description of all menus and their components should be included
True Possible constraints placed on the database designer, including speed requirements, hardware platforms, and so on. A description of the graphical user interface (GUI). If the GUI is menu-driven, a description of all menus and their components should be included
TRUE / FALSE A requirements document can contain the following types of information: Descriptions of operational scenarios. A scenario is a proposed specific use of the database system. More specifically, a scenario is a description of one or more beginning-to-end transactions involving the database system and its environment.
True Descriptions of operational scenarios. A scenario is a proposed specific use of the database system. More specifically, a scenario is a description of one or more beginning-to-end transactions involving the database system and its environment.
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Database tuning capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Utilities
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Performance monitoring A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Utilities
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Support for database administration A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Utilities
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Use monitoring A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Utilities
TRUE / FALSE A requirements document can contain the following types of information: Possible constraints placed on the database designer, including speed requirements, hardware platforms, and so on. A description of the graphical user interface (GUI). If the GUI is menu-driven, a description of all menus and their components should not be included, discussions about the GUI is conducted only during the " implement database phase"
false Possible constraints placed on the database designer, including speed requirements, hardware platforms, and so on. A description of the graphical user interface (GUI). If the GUI is menu-driven, a description of all menus and their components should be included
TRUE / FALSE A requirements document can contain the following types of information: An arbitrary or vague mission statement for the organization in relation to the database. A mission statement declares the specific purpose of the database in broad terms without defining specific tasks pertinent to the implementation of the database. An arbitrary mission statements leave room for further development
false A well-defined mission statement for the organization in relation to the database. A mission statement declares the specific purpose of the database in broad terms without defining specific tasks pertinent to the implementation of the database.
TRUE / FALSE A requirements document can contain the following types of information: The data and processing requirements for all participating departments, individuals, and so forth.
true The data and processing requirements for all participating departments, individuals, and so forth.
One of the fundamental activities that go into creating a requirements document is conducting no interviews The following are a few suggestions that can help make the interview process a successful one: A) Limit the number of people interviewed at one time B) Group interviews will increase efficiency C) Interview management personnel separately from users D) provide the interviewees with a list of the topics E) allow interviewees to dictate the flow of the interview F) Ensure that someone adept at notetaking attends
Limit the number of people interviewed at one time Try to interview management personnel separately from users Before conducting the interview, provide the interviewees with a list of the topics of discussion Ensure that someone adept at notetaking attends the interviews or record the interviews yourself.
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Architecture (two-tier or three-tier) A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Extensibility/scalability/portability A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Hardware requirements A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Product documentation OS requirements A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Purchase cost A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Training availability/cost A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Vendor reputation/stability A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Vendor support/online support A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Miscellaneous features
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Available file structure A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Hard disk requirements A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Indexing capabilities A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Memory requirements A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Support for data compression A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Bellow is a listed description of a criteria for selecting a DBMS, which criteria does this description fall under: Support for encryption A) Data definition functionality B) Physical criteria C) Access criteria D) Transactions E) Utilities F) Development tools G) Miscellaneous features
Physical criteria
Someone other than the database designer or developer should test the database and the application accessing the database. ___ Someone who has no knowledge of the code, or any predetermined notions of how the application is supposed to perform, conducts this type of testing. This individual should test as many aspects as possible of the database and the application from the user's point of view, including all areas of user input, user interface, and data output areas. This individual should be instructed to try to break the application by trying all types of data input. A) Glass- box B) Clear- box C) White- box D) Dark-box E) Black- box
"black-box" testing. Someone who has no knowledge of the code, or any predetermined notions of how the application is supposed to perform, conducts this type of testing. This individual should test as many aspects as possible of the database and the application from the user's point of view, including all areas of user input, user interface, and data output areas. This individual should be instructed to try to break the application by trying all types of data input.
