Every database design project should start with a clear understanding of what the project's goals are. The focus should be on what the database needs to do, not how the database needs to do it.
- [Instructor] Every database design project…should start with a clear understanding…of what the goals of the project are.…The focus should be on what the database needs to do…at a very high level…and not how the database needs to do it.…To this end, we're going to start the design process…with a well thought through mission statement.…The mission statement will be the guidepost…that we can always refer back to…in order to make sure that the development process…is proceeding on course.…It can help prevent what's referred to as "scope creep,"…where new features and enhancements continually get added…to the project and the database never seems to get finished.…
The mission statement is developed in conjunction…with the initiator of the project.…Typically, this is the person that gave the green light…to proceed after the planning phase,…where the need for a new database was initially requested.…This could be a member of the management team,…or the head of the organization.…It should be as focused as possible when defining the goal…
Adam Wilbert covers the basics of relational database design, regardless of whether you use Access, FileMaker, Open Office, or SQL Server. Learn how to prevent data anomalies, gather requirements to plan your design, and develop a conceptual data model—translating your ideas into components like tables, relationships, queries, and views. Plus, learn about logical design considerations that can help you construct a database that is easy to maintain.
- What is a database management system (DBMS)?
- Moving through the database development cycle
- Preventing duplicate, inconsistent, and conflicting data entries
- Gathering requirements
- Developing relationships
- Identifying key fields
- Following a naming convention
- Developing the actual database
Skill Level Beginner
1. Relational Database Basics
Relational structures3m 46s
2. Preventing Data Anomalies
3. Gathering Requirements
4. Developing the Conceptual Data Model
5. Normalizing Your Data
6. Logical Design Considerations
7. Developing the Physical Database
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.