1
Q
- p 305. MODELING YOUR DATABASE. When you set out to design a database, you need to do upfront planning by creating an:
A
ENTITY RELATIONSHIP DIAGRAM
2
Q
- The FIRST step in designing a database is:
A
deciding what tables you need and how they fit together.
3
Q
- Since EVERY TABLE HOLDS DATA ABOUT A SINGLE ENTITY, you normally start by:
A
figuring out all the ENTITIES in your system.
4
Q
- You start to figure out the entitites you need by:
A
LISTING ALL THE THINGS YOUR DATABASE WILL NEED TO DO. What do you do every day? What do you wish you could do? What information do you need to do it?
5
Q
- Once you have a list of all the things the database will need to do, you can start to figure out what ENTITIES the database will need to track. For each item on the list, you:
A
try to think of all the things it involves.
6
Q
- If your list has an item shown as: KEEP TRACK OF THE PEOPLE I DO BUSINESS WITH AND THE JOBS I DO FOR THEM, then the THINGS IT INVOLVES might be:
A
CUSTOMERS, JOBS, COMPANIES
7
Q
- If the item is TRACK EXPENSES INCURRED WHILE DOING WORK FOR CUSTOMERS, the THINGS IT INVOLVES might be:
A
EXPENSES, AIRLINE TICKETS, HOTELS, FILM.
8
Q
- An item called CREATE INVOICES might INVOLVE THINGS like:
A
INVOICES, LINE ITEMS, ADDRESSES.
9
Q
- KEEP TRACK OF WHAT I’M OWED AND WHAT I’VE BEEN PAID might INVOLVE THINGS like:
A
PAYMENTS, CHECKS, OUTSTANDING BALANCES.
10
Q
- TRACK MY TIME, WHAT I DID, FOR WHOM, AND FOR HOW LONG might INVOLVE THINGS like:
A
TASKS, SERVICES.
