1. Database Design Process

2. The Steps 1.What does the database/application need to do? 2.Develop the tables 3.Establish relationships 4.Set up the forms and sub-forms 5.Set up the queries 6.Set up the reports

3. What does the database/application need to do? What is the goal? – A goal is the statement of what the end-user or business wants (defining the problem) We need to make the process more efficient We want to increase the speed and make the system more user friendly Your job is to find out what they really mean and want

4. What does the database/application need to do? Gathering requirements – What are they currently doing? – What is working? – What is not working? – If they could make changes what would they be? – End-user levels – Surveys, interviews and shadowing – Other

5. What does the database/application need to do? Watch for these mistakes – Input from people who do not use the system day- to-day – ‘Wish List’ that will cost $$$$$$ – People who think they know what the database can do, but really don’t – Extensive system that will create total reformatting of existing database

6. Once Data is Collected Conceptual Model – For person/group that provided the goal statement – Steps needed for project – Not extremely specific Tables that will contain the customer data and invoices Forms that will … Reports that will show …

7. Conceptual Model  Scope Development – Review all of the data collected – Identify the fields (entities) Person, place, items, concepts – Properties of the fields (attributes) Data types Text – number of characters – Relationships Connections – How data is perceived by the business users

8. Scope of the Project Check list for the developer All items needed Timeline Assignment Other information needed Frequently attached to the contract

9. Scope  Logical Model Logical model – taken from the scope – Specific steps of what is needed – Tables – Forms, queries, reports – Data storage, availability, reliability, scalability – Security Access, permissions

10. Logical Model How data is perceived by the programmers – Tables – Fields with properties Constraints PK & FK – Relationships 1 to 1 1 to Many Many to Many

11. Physical Model Physical storage of the data – Most frequently used tables – Rarely used tables – Archives Administered by – Network Admin – Database Admin Technologies used