Database Systems: Design, Implementation, & Management
Database Systems: Design, Implementation, & Management
12th Edition
ISBN: 9781305627482
Author: Carlos Coronel, Steven Morris
Publisher: Cengage Learning
bartleby

Concept explainers

Question
Book Icon
Chapter 9, Problem 2P

a)

Program Plan Intro

Creation of an information system:

  • To create an information system an initial study and following phases are need to be made by the designer because they will create an impact to the design of the database.
  • The information is collected in order to establish details about the entities, relationships among the entities generated.
  • Business rules that are shaped up through relationships, connectivity and cardinalities are being obtained and collected through designer.

Question that can be asked in order to create an information system:

The below are some of the sample questions that can impact the design of the database:

  • Is it required to develop the database for all departments at once or whether it is required to design and implement the database for one particular department?
  • What will the design approach required that could affect the process of designing?
  • What type of development is required, one module at a time or integrated system approaches (Example: Billing, production, shipping and inventory)?
  • What type of tracking system is required that is in terms of tracking the nuts and bolts through lot number, by shift, by production, by type or by department?
  • What type of tracking system is required for the suppliers of each batch that is in terms raw materials used in the production of the nuts and bolts?
  • Is it required to track the customer information regarding the receive summary of nuts and bolts based on batches?
  • What type of reporting system is required that is what type of reporting requirements are required and who requires the distribution report details needs to be specified?

    Effect of the questions that are asked:

The answers to the above question affect the database design in conceptual and in logical way along with the implementation, testing made with the subsequent operations.

b)

Program Plan Intro

Creation of an information system:

  • To create an information system an initial study and following phases are need to be made by the designer because they will create an impact to the design of the database.
  • The information is collected in order to establish details about the entities, relationships among the entities generated.
  • Business rules that are shaped up through relationships, connectivity and cardinalities are being obtained and collected through designer.

Question that can be asked in order to create an information system:

The below are some of the sample questions that can impact the design of the database:

  • Is it required to develop the database for all departments at once or whether it is required to design and implement the database for one particular department?
  • What will the design approach required that could affect the process of designing?
  • What type of development is required, one module at a time or integrated system approaches (Example: Billing, production, shipping and inventory)?
  • What type of tracking system is required that is in terms of tracking the nuts and bolts through lot number, by shift, by production, by type or by department?
  • What type of tracking system is required for the suppliers of each batch that is in terms raw materials used in the production of the nuts and bolts?
  • Is it required to track the customer information regarding the receive summary of nuts and bolts based on batches?
  • What type of reporting system is required that is what type of reporting requirements are required and who requires the distribution report details needs to be specified?

    Effect of the questions that are asked:

The answers to the above question affect the database design in conceptual and in logical way along with the implementation, testing made with the subsequent operations.

Blurred answer
Students have asked these similar questions
This is a question that I have and would like someone who has experiences with scene graphs and entity component systems to answer.For context, I am currently implementing a game engine and currently I am debating on our current design.Our current design is we have a singular game component class that every component inherits from. Where we have components like SpriteRendererComponent, Mehs Component, etc. They inherit from this GameComponent class. The point of this is being able to have O(1) access to the scene to being able to modify components to attach more components with the idea of accessing those components to specific scene objects in a scene.Now, my question is what kinds of caveauts can this cause in terms of cache coherence? I am well aware that yes its O(1) and that is great but cache coherence is going to be really bad, but would like to know more explicit details and real-life examples such as write in RAM examples on how this is bad. A follow-up question that is part…
Q4: Consider the following MAILORDER relational schema describing the data for a mail order company. (Choose five only). PARTS(Pno, Pname, Qoh, Price, Olevel) CUSTOMERS(Cno, Cname, Street, Zip, Phone) EMPLOYEES(Eno, Ename, Zip, Hdate) ZIP CODES(Zip, City) ORDERS(Ono, Cno, Eno, Received, Shipped) ODETAILS(Ono, Pno, Qty) (10 Marks) I want a detailed explanation to understand the mechanism how it is Qoh stands for quantity on hand: the other attribute names are self-explanatory. Specify and execute the following queries using the RA interpreter on the MAILORDER database schema. a. Retrieve the names of parts that cost less than $20.00. b. Retrieve the names and cities of employees who have taken orders for parts costing more than $50.00. c. Retrieve the pairs of customer number values of customers who live in the same ZIP Code. d. Retrieve the names of customers who have ordered parts from employees living in Wichita. e. Retrieve the names of customers who have ordered parts costing less…
Q4: Consider the following MAILORDER relational schema describing the data for a mail order company. (Choose five only). (10 Marks) PARTS(Pno, Pname, Qoh, Price, Olevel) CUSTOMERS(Cno, Cname, Street, Zip, Phone) EMPLOYEES(Eno, Ename, Zip, Hdate) ZIP CODES(Zip, City) ORDERS(Ono, Cno, Eno, Received, Shipped) ODETAILS(Ono, Pno, Qty) Qoh stands for quantity on hand: the other attribute names are self-explanatory. Specify and execute the following queries using the RA interpreter on the MAILORDER database schema. a. Retrieve the names of parts that cost less than $20.00. b. Retrieve the names and cities of employees who have taken orders for parts costing more than $50.00. c. Retrieve the pairs of customer number values of customers who live in the same ZIP Code. d. Retrieve the names of customers who have ordered parts from employees living in Wichita. e. Retrieve the names of customers who have ordered parts costing less than$20.00. f. Retrieve the names of customers who have not placed…
Knowledge Booster
Background pattern image
Computer Science
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
SEE MORE QUESTIONS
Recommended textbooks for you
Text book image
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Text book image
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning