DB section has been updated to add some SQL code.
A database can be defined as a structured collection of data around a particular subject.
They are not new. Databases can be paper or electronic. If they are electronic they can use a Database Management System or a Relational Database Management System to create and manipulate the data.Â
There are numerous disadvantages to paper databases with the gallery to the right showing some of these:
Data and Information are two separate concepts. Data is simply number or text without context such as: 14976. Information is data that has been given context or meaning. Such as DOB: 14/9/76.
65 is data. But if it is given context such as age or height it can take on different meaning and be classed as information.
DD3 0HB is data. But if it is given context such as postcode or car reg it can take on different meaning and be classed as information.
When we are first designing a database the client will probably have a collection of data they want to store. Such as in the furniture example we will be making in the next sections.
It is a database for a small furniture company that will store the data about the items it sells and the designers that design them.
The end user requirements are from the people who will be using the system. So initial comments may be:
I need to be able to find all of the items designed by a particular designer
I need to be able to see all of the items we have in stock
I want to be able to see all of the items that are out of stock
I need to display all categories of furniture in order of price
I need to be able to find the email address of a designer
I need to add new designers and furniture items
I need to change the amount in stock or the price of an item
I will need to remove items that we will no longer be selling.
These may be refined into:
Staff should be able to search the database on the following fields:
Designer,Number in Stock,Category,Designer Name, Designer Email Address
Search results should display the following fields:
Designer Name, Email Address and Phone Number
Item Name, Description, Price, Type, Quantity
These can then be converted into functional requirements such as:
The database shall be a relational database system with two tables. One holding designer details and one for the items of furniture.
Designer ID and Item ID will be additional fields used as Primary Keys.