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_forwardSpecification Suppose you are asked to design a club database system based on the _following information. Each student has a unique student id, a name, and an email; each club has a unique club id, a name, a contact telephone number, and has exactly one student as its president. Each student can serve as a president in at most one of the clubs, although he/she can be the members several clubs. Clubs organize activities and students can participate in any of them. Each activity is described by a unique activity id, a place, a date, a time and those clubs that organize it. If an activity is organized by more than one club, different clubs might contribute different activity fees. Question Draw an E-R diagram for the system according to the above description.arrow_forward
- Are there any fundamental decisions to be made when it comes to physical database design?arrow_forwardDraw an E-R diagram for the description below. Suppose that you are asked to model a database including all pharmaceutical companies, their drugs, and all pharmacies. Each pharmaceutical company is identified by its name and has a phone number. For each drug, the trade name (e.g., Acetaminophen) and formula must be recorded. Each drug is sold by only one pharmaceutical company, and the trade name identifies a drug uniquely from among the products of that company. If a pharmaceutical company stops production, we do not need to keep track of its products any longer. Each pharmacy has an identifier name, address, and phone number. Each pharmacy sells several drugs. A drug could be sold at several pharmacies, and the price could vary from one pharmacy to another.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
- Draw 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_forwardIn the case of a physical database, where do you begin?arrow_forwardConstruct the ER diagram for the NHL database using the Crows Foot notation Suppose you are given the following requirements for a simple database for the National Hockey League (NHL):• the NHL has many teams,• each team has a name, a city, a coach, a captain, and a set of players,• each player belongs to only one team,• each player has a name, a position (such as left wing or goalie), a skill level, and a setof injury records,• a team captain is also a player,• a game is played between two teams (referred to as host_team and guest_team) andhas a date (such as May 11th, 2017) and a score (such as 4 to 2).arrow_forward
- Problem: 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_forwardImagine 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_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