Fernando Cilebra has always ben facinated by skateboards. Fernando has won several contests, both locally and nationally. His interest in skateboards led him to open Fernando's Shop in Denton, Maine. Fernando sells street, trick, and children's skateboards. The store has only been open for a couple of months, yet sales have been very high. Recently, Fernando has come to realize that he will need some help to manage the information his busines is creating. He has contacted you to help him design a database.

After meeting with Fernando, you have learned that h purchases the skateboards he sells from three suppliers, but he plans to add new suppliers in the near future. Fernando has realistic expectations that his business will continue to grow, and soon, he will be unable to manage the information on suppliers and products. He realizes the database will need to contain two tables: a supplier table and a product table. He also know that there will have to be a relationship between the two tables. Now, he needs your help to complete the design.

1. Define and explain the traditional database design method ( hierarchical, network, and rational).
2. Describe how you would follow the three phases of the traditional database design method (hierarchical, network, and rational), considering the scenario given.
3. Include one assumption and one sample data to complete the process. All answers should be detailed and in complete format.

1. Traditional Database Design Methods:

a) Hierarchical: This method organizes data in a tree-like structure with a strict parent-child relationship. Each parent can have multiple children, but each child can only have one parent. It was commonly used in early database systems and is effective for simple data relationships. However, it lacks flexibility in handling complex relationships and can lead to data redundancy.

b) Network: This method extends the hierarchical model by allowing more complex relationships between records. Instead of a strict one-to-many relationship, it supports many-to-many relationships by using a linking concept called "sets" or "networks." This model allows for more flexibility in representing complex data structures but can become cumbersome to maintain and query.

c) Relational: The relational model organizes data into tables, where each table represents an entity and each row represents a record. It emphasizes the relationships between tables through the use of primary and foreign keys. This model provides a flexible and efficient way to manage data and is widely used in modern database systems.

2. Following the Three Phases of Traditional Database Design:

a) Hierarchical: In this phase, the database designer would identify the key entities, such as suppliers and products, and their relationships. Based on the scenario, Fernando's Shop has a hierarchical structure where suppliers are at the top level and products are connected to suppliers. The designer would create a supplier table with a primary key of the supplier ID and a product table with a foreign key linking it to the supplier ID.

b) Network: In this phase, the designer would identify the many-to-many relationships and create sets or networks to represent them. However, since Fernando's Shop scenario does not have any explicit many-to-many relationships, this phase may not be applicable.

c) Relational: In this phase, the designer would focus on normalizing the tables to eliminate redundancy and ensure data integrity. The designer would review the attributes of the supplier and product tables, ensuring that each attribute captures a single, atomic piece of data. For example, in the supplier table, there could be attributes like supplier ID, supplier name, contact information, etc. Similarly, the product table could have attributes like product ID, product name, price, etc. The relationships between the tables would be established by including the foreign key in the appropriate table.

3. Assumption and Sample Data:

Assumption: Each product can only be supplied by one supplier.

Sample Data:

Supplier Table:
| Supplier ID | Supplier Name | Contact Information |
|-------------|------------------|------------------------------|
| 1 | ABC Skate Supply | abc |
| 2 | XYZ Board Shop | xyzboardshop|

Product Table:
| Product ID | Product Name | Price |
|------------|----------------|-------|
| 1 | Street Deck | 50.00 |
| 2 | Trick Deck | 60.00 |
| 3 | Children's Deck| 40.00 |

The sample data showcases two suppliers, ABC Skate Supply and XYZ Board Shop, and three products: Street Deck, Trick Deck, and Children's Deck. Each product is associated with a single supplier. This data can be used as a starting point for building the database and managing the information for Fernando's Shop.