Concept explainers
a)
Creation of an
- 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)
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.
Trending nowThis is a popular solution!
Chapter 9 Solutions
Database Systems: Design, Implementation, & Management
- Using a graphics program, develop an entity-relationship diagram for a database application for an Internet bookstore where students buy textbooks from a salesperson and receive invoices for their purchases. Use Figure 5.5 as a guide.arrow_forwardA new sales ordering system needs a relational database that contains a customer table, a product inventory table, and an order table. Use a word-processing, graphics, or spread-sheet program to draw an entity-relationship diagram showing the relationships among these entities. Next, design each of these tables showing the keys and attributes to be included in each table. Include five sample records for each table.arrow_forwardI understand the purpose of a database, which is to make data record-keeping easier for any company. And I'm aware of the hardware requirements. The concept of programming the rules and structure of a database is the area in which I am most confused. A database, in my mind, is a chart (or many charts) containing fields that are used to hold records. Then, of course, those records in one chart interweave with those in other charts, necessitating the creation of chart linkages. The concept of developing a framework for the data to fit into is where I get stuck. Are we creating metaphysical venues to store data, or are we just recording relationships between data saved on a variety of platforms?arrow_forward
- Question : Draw the EER diagram that describes the following scenario: ( PLEASE EXPLAIN STEP BY STEP AND IN DETAIL) We want to design a database for keeping track of information about votes taken is the PAKISTAN PROVISIONS in the current administration. They include the PARLIAMENT and the SENATE. A MINISTER in the PAKISTAN is either a Parliament Member or a Senator depending on to which body they are elected to. The database needs to keep track of each PAKISTAN CITY’s Name (e.g., ‘Lahore’, ‘Karachi’, ‘Multan’) and include the Region of the country to which the city belongs (whose domain is {‘Punjab’, ‘Sind’, ‘KPK’, ‘Baluchistan’}) and its population in the 170 million. Each MINISTER is described by his or her Name, plus the District represented, the Start_date when the parliament was first elected, and the political Party to which he or she belongs (whose domain is {‘PPP’, ‘PTI’, ‘PML(N)’, ‘PML(Q)’, ‘ANP’, ‘MQM’, ‘Independent’, ‘Other’}). A city can have a number of parliament…arrow_forwardDraw the ER diagram based on the following specification. A tutorial school is using a database to manage information about teachers, courses, and students. Each teacher is identified by staff_id, has a name, an email address, and a phone number. Each student is identified by student_id, has a name, an email address, and a registration date. Each course is identified by course_id, year, and semester. In addition, each course has a name. Each course is associated with multiple lessons. A lesson has a lesson number, a location, a date, a start-time, and an end-time. Lesson numbers are sequentially numbers, starting from 1, generated separately for each course. Each teacher teaches at least one course. Each student takes at least one course. Each course is taught by one teacher. Each course can be taken by many students.arrow_forwardWhat makes Database unique as a programming language? Give me an illustration, please, since I don't get it without one.arrow_forward
- I understand the intentions of a database, being to streamline the data record-keeping of any organizations. And I understand the hardware needed to do such. The area I find myself the most lost in is the idea of programming the rules and structure of a database. In my head a database is a chart (or multiple charts) with fields that is used to store records. And then those records stored in one chart intertwine with other charts of course so we need to have relationships between the charts. Where I get lost is in the thought of programming a structure for the data to fit in. Are we making metaphysical locations to store data or are we just writing relationshipds between data that is stored on a plethora of different options?arrow_forwardProblem: Your team of Data Analysts have been asked to create a database design for the Boeing X Aircraft Company (BAC), which has two HUD (heads-up display) products: TRX-5A and TRX-5B. The database must enable managers of BAC to track blueprints, parts, and software for each HUD, using the following business rules: For simplicity’s sake, you may assume that the TRX-5A unit is based on two engineering blueprints and that the TRX-5B unit is based on three engineering blueprints. You are free to make up your own blueprint names. All parts used in the TRX-5A and TRX-5B are classified as hardware. For simplicity’s sake, you may assume that the TRX-5A unit uses three parts and that the TRX-5B unit uses four parts. You are free to make up your own part names. BAC wants to keep track of all part price changes and the dates of those changes. BAC wants to keep track of all TRX-5A and TRX-5B software. For simplicity’s sake, you may assume that the TRX-5A unit uses two named software components…arrow_forwardYour Division Head's point of view is as follows: "Pictures are stored in a database, and the basic design/structure we chose includes some very sensitive driver information." What if we placed it in its own folder, out of reach of people who shouldn't have access to it? What would your stance be, or, more precisely, which strategy would you prefer? It is necessary to present justification.arrow_forward
- Imagine for a moment the culture of a small or medium-sized business. Is there anything that, due to social or cultural considerations, stands in the way of the general adoption of a big data application or a NoSQL database? If this is the case, how should we approach dealing with them in the years to come?arrow_forwardIt's important to note that doing a search using keywords on the internet and conducting a search using keywords on a database are two entirely different processes. Both of these things are quite different from one another. What are some of the most significant differences that exist between the two in terms of how the inquiries are expressed and what the results of a query are, and what are some of the most significant similarities that exist between the two in terms of how the inquiries are expressed and what the results of a query are?arrow_forwardCreate a database schema design based on the following (simplified) requirements of the COMPANY Database: 1. The company is organized into DEPARTMENTs. Each department has a name, number and an employee who manages the department. We keep track of the start date of the department manager. A department may have several locations. 2. Each department controls a number of PROJECTs. Each project has a name, a unique number, and a brief description. 3. We store each EMPLOYEE's social security number, address, salary, gender, and birthdate. a) Each employee works for one department but may work on several projects, which are not necessarily controlled by the same department. b) We keep track of the number of hours per week that an employee currently works on each project. c) We also keep track of the direct supervisor of each employee. 4. Each employee may have a number of DEPENDENTs. a) For each dependent, we keep track of their name, gender, birthdate, and relationship to the employee. We…arrow_forward
- Principles of Information Systems (MindTap Course...Computer ScienceISBN:9781305971776Author:Ralph Stair, George ReynoldsPublisher:Cengage LearningPrinciples of Information Systems (MindTap Course...Computer ScienceISBN:9781285867168Author:Ralph Stair, George ReynoldsPublisher:Cengage Learning