30 Questions
Match the following phases of the SDLC with their corresponding activities:
Planning = Writing programs, building databases, testing, installing, training, and documenting Analysis = Preliminary understanding of business situation, and conceptual data modeling Design = Thorough analysis of business situation, leading to functional requirements Implementation = Logical and physical database design, to develop technology and organization
Match the following database development approaches with their characteristics:
SDLC = Cursory attempt at conceptual data modeling Prototyping = Time-consuming, but comprehensive
Match the database project team members with their primary responsibilities:
Business analysts = oversee the projects, manage the personnel Database analysts = analyze business situation and establish requirements Project managers = ensure data integrity and consistency Systems analysts = have technical expertise for overall information systems
Match the following SDLC phases with the outputs they produce:
Planning = Functional requirements Analysis = Enterprise model and conceptual data modeling Design = Detailed conceptual data modeling Implementation = Logical and physical database design
Match the database project team members with their primary responsibilities:
Users = coders of the programs that interact with the database Programmers = communicate their needs to analysts Data administrators = establish standards for data in business units Database architects = responsible for existing databases
Match the following database development activities with their corresponding SDLC phases:
Monitoring, repairing, and enhancing = Planning Writing programs, building databases, testing, installing, training, and documenting = Design Preliminary understanding of business situation, and conceptual data modeling = Implementation Logical and physical database design, to develop technology and organization = Maintenance
Match the objectives driving the evolution of database systems with their descriptions:
Need for program-data independence = ease of data access for less technical personnel Desire to manage more complex data types and structures = reduce maintenance Ease of data access for less technical personnel = manage more complex data types and structures Need for more powerful decision support platforms = need for program-data independence
Match the database project team members with their primary responsibilities:
Data modelers = focus on database Other technical experts = analyze business situation and establish requirements Database analysts = network, operating system, documentation, etc. Systems analysts = establish standards for data in business units
Match the following database development approaches with their development cycle characteristics:
SDLC = Rapid development cycle Prototyping = Rapid development cycle
Match the database project team members with their primary responsibilities:
Database architects = ensure data integrity and consistency Data administrators = coders of the programs that interact with the database Programmers = establish standards for data in business units Project managers = analyze business situation and establish requirements
Match the following SDLC phases with the activities that occur during them:
Planning = Thorough analysis of business situation, leading to functional requirements Analysis = Preliminary understanding of business situation, and conceptual data modeling Design = Monitoring, repairing, and enhancing Maintenance = Logical and physical database design, to develop technology and organization
Match the objectives driving the evolution of database systems with their descriptions:
Desire to manage more complex data types and structures = need for more powerful decision support platforms Need for program-data independence = manage more complex data types and structures Need for more powerful decision support platforms = reduce maintenance Ease of data access for less technical personnel = need for program-data independence
Match the following data models with their descriptions:
Enterprise Data Model = High-level entities and relationships for the organization Project Data Model = A detailed view, matching data structure in database or data warehouse Graphical Diagram = Capturing nature and relationship of data Relational Databases = Database technology involving tables and keys
Match the following database concepts with their explanations:
Entities = Noun form describing a person, place, object, event, or concept Attributes = Composed of relationships Relationships = Between entities, usually one-to-many or many-to-many Primary/Foreign Keys = Representing data structure in database or data warehouse
Match the following data model types with their characteristics:
Segment of an Enterprise Data Model = More detailed view of entities and relationships Segment of a Project Data Model = High-level view of entities and relationships Relational Databases = Database technology involving tables and relationships Graphical Diagram = Capturing detailed nature of data
Match the following database concepts with their relationships:
One-to-One (1:1) = Relationships between entities, usually one-to-many or many-to-many One-to-Many (1: N) = Relationship between entities, one entity to multiple entities Many-to-Many (M: N) = Relationship between entities, multiple entities to multiple entities Primary/Foreign Keys = Relationship between entities, one entity to one entity
Match the following data models with their purposes:
Graphical Diagram = Capturing nature and relationship of data for a project Enterprise Data Model = High-level entities and relationships for the organization Project Data Model = Capturing detailed nature and relationship of data for the organization Relational Databases = Database technology for capturing data relationships
Match the following database concepts with their descriptions:
Attributes = Noun form describing a person, place, object, event, or concept Entities = Composed of attributes and relationships Relationships = Capturing nature and relationship of data Primary/Foreign Keys = Between entities, usually one-to-many or many-to-many
Match the following database types with their typical size:
Personal Databases = Megabytes Departmental Databases = Gigabytes Enterprise Applications = Terabytes or Petabytes Client/Server Databases = Kilobytes
Match the following database types with their intended user base:
Personal Databases = One user Departmental Databases = Several users, usually doesn’t exceed 100 Enterprise Applications = Company-wide, very large user base Client/Server Databases = Department-wide
Match the following database architectures with their corresponding figure number:
Multi-Tiered Client/Server Database Architecture = Figure 1-12 Database Technologies = Figure 1-11 Personal Databases = Figure 1-10 Enterprise Applications = Figure 1-13
Match the following database types with their corresponding description:
Departmental Databases = Intended for several users, usually doesn’t exceed 100 Enterprise Applications = Typical size in the gigabytes, terabytes, or even petabytes Personal Databases = Typical size in the megabytes Client/Server Databases = Intended for one user
Match the following database types with their scope:
Personal Databases = Single user, local scope Departmental Databases = Department-wide scope Enterprise Applications = Company-wide scope Client/Server Databases = Global scope
Match the following database architectures with their complexity:
Personal Databases = Simple Departmental Databases = Moderate Enterprise Applications = Complex Multi-Tiered Client/Server Database Architecture = Basic
Match the following types of enterprise systems with their characteristics:
Enterprise Systems = Maintain historical data Data Warehouses = Integrates data from multiple data sources Data Lakes = Backbone of an organization ERP = Large integrated repository for internal and external data
Match the following terms with their descriptions:
Data Warehouses = Large integrated repository for internal and external data Data Lakes = Integrates data from multiple data sources and maintain historical data ERP = Typically involve relational databases Supply Chain Management = Help identify patterns and trends
Match the following concepts with their applications:
Executive Dashboard = Database Evolution at Pine Valley Furniture Company Customer Relationship Management = An Example of an Executive Dashboard Project Planning = Courtesy Tableau Software Human Resource Management = Pine Valley Furniture Company
Match the following topics with their chapters:
Database Evolution = Chapter 1 Designing the Database = Chapter 2 Administering the Database = Chapter 1 Future of Databases = Chapter 3
Match the following figures with their descriptions:
Figure 1-13 = An Example of an Executive Dashboard Figure 1-1 = Pine Valley Furniture Company Figure 1-2 = Database Evolution at Pine Valley Furniture Company Figure 1-14 = Courtesy Tableau Software
Match the following acronyms with their meanings:
ERP = Electronic Resource Planning PVF = Pine Valley Furniture Company SQL = Server Query Language CRM = Customer Relationship Management
Test your understanding of database management systems, including data models, entity relationships, and enterprise data models. Learn about the challenges of old file processing systems and the benefits of a database approach.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
