Six-Step Relational Database Design™ (Second Edition): A Step by Step Approach to Relational Database Design and Development by Fidel A. CaptainThe second edition contains a new chapter on implementation that goes through the steps necessary to implement each of the case studies on a relational database management system, clearly relating the design to implementation and database theory. In addition, questions are also included at the end of each of the six steps and one of the previous case studies has been replaced, making the case study selection more diverse.
Six-Step Relational Database Design™ bridges the gaps between database theory, database modeling, and database implementation by outlining a simple but reliable six-step process for accurately modeling user data on a Crows Foot Relational Model Diagram, and then demonstrating how to implement this model on any relational database management system.
Six-Step Relational Database Design™ uses three case studies and starts with a statement of the problem by the client and then goes through the six steps necessary to create a reliable and accurate data model of the clients business requirements. This model can then be used to implement the database on any relational database management system.
Six-Step Relational Database Design™ should be used as a handbook for students and professionals in the software-development field. The technique described in this book can be used by students for quickly developing relational databases for their applications, and by professionals for developing sturdy, reliable, and accurate relational database models for their software applications.
A Quick-Start Tutorial on Relational Database Design
A core aspect of software engineering is the subdivision of the development process into a series of phases, or steps, each of which focuses on one aspect of the development. The software product moves through this life cycle sometimes repeatedly as it is refined or redeveloped until it is finally retired from use. Ideally, each phase in the life cycle can be checked for correctness before moving on to the next phase. Let us start with an overview of the waterfall model such as you will find in most software engineering textbooks. This waterfall figure, seen in Figure It shows the process as a strict sequence of steps where the output of one step is the input to the next and all of one step has to be completed before moving onto the next. We can use the waterfall process as a means of identifying the tasks that are required, together with the input and output for each activity.
It has since become the dominant database model for commercial applications in comparison with other database models such as hierarchical, network and object models. A relational database organizes data in tables or relations. A table is made up of rows and columns. A row is also called a record or tuple. A column is also called a field or attribute. A database table is similar to a spreadsheet.
The database design process
Comment 0. When designed correctly, databases are incredibly powerful tools for recording, storing, retrieving, and comparing data. When building a database — regardless of its ultimate purpose — adhering to the following best practices will ensure that the final product that is both useful and easy to use. There are a number of techniques available today, such as Scrum and RAD rapid application development , which help IT teams to develop databases at a rapid pace. When speed and efficiency are being leveraged by institutions to force a quick build, it can be tempting to dive straight into constructing a database with only a vague notion of what the outcome needs to be.