You are asked to assume that the data model has been agreed and you are given an entity relationship diagram and the names of the attributes of some of the entities. You are not, however, given a detailed data model (for example, including domains, data types and constraints) because we ask you to make decisions about these things in the assignment.

Here the users of the DBMS are customers. The Customers data needs to be stored as a customer table. The customer table will be having all the details about the customer like customer number, customer name, customer phone number and customer address. As given in the scenario Customer address may not be present. The value which is very unique should be the primary key. As per that definition, each and every customer will be having customer number. Not two customers will be having same customer number and not two customer numbers can go to a same customer. Hence customer number will be considered for a primary key. The customer number can have customer address along with phone number. Most of the data fields are variables and they are CHAR type. Only the phone number can be a number and it is an INTEGER type.

1(b)(i)

The preceding steps contain the database design process:

1. Firstly, determine your database’s purpose
   It helps you to prepare for the rest of the steps.
2. Secondly search and arrange the required information
   Collect all the types of information you would require for recording in the database like name of the product and its order number.
3. Then create table and segregate all the information
   Information will be divided into entities or subjects. Each entity will result a table.
4. Next create columns for the information items
   Choose what data you need to store in every table. Everything turns into a field, and is shown as a section in the table. For instance, an Employees table may incorporate fields, for example, Last Name and Hire Date.
5. Further mention the primary keys
   Pick every table's primary key which is a segment that is utilized to interestingly distinguish every column. A case may be Product ID or Order ID.
6. Then next set up the table relationships
   Take a gander at every table and choose how the information in one table is identified with the information in different tables. Add fields to tables or make new tables to illuminate the connections, as important.
7. And then refine your design
   Investigate your outline for mistakes. Make the tables and include a couple records of test information. Check whether you can get the outcomes you need from your tables. Do the adjustments as per the requirement.
8. And apply the normalization rules
   Normalization rules needs to be applied and the results needs to be obtained.

1(b)(ii)

Almost any database needs a client interface to include, recover, overhaul and erase records, known by the ugly acronym CRUD. There are various administrator applications that give such nonexclusive facilties. For instance, for PostgreSQL we have pgAdmin which offers a GUI and phpPgAdmin and Adminer which offer PHP web interfaces. These have a few impediments. The improvement of user interfaces (UIs), extending from ahead of schedule prerequisites to programming out of date quality, has turned into a period expending and excessive procedure. Normally, the graphical user interface (GUI) of an intelligent framework speaks for around 48% of the source code, requires around 45% of the advancement time and half of the usage time and covers 37% of the support time. These figures, assessed in the midnineties, are expanding significantly with the spread of new communication systems, for example, vocal and gestural modalities, bringing about extra necessities.

Distributed Database Concept

CPU is a memory which has database that is detached to handling unit. It screens by the dispersed framework of database administration. The information is stored in different PCs. They might vanish at an end of systems of ward PCs and might likewise stay in the first areas. In conflicting to the parallel frameworks that has firmly coupled processor and build up single database framework then the circulated database framework are approximately combined without segments actually associated physically.

In the distributed database the information is orchestrated with the assistance of framework managers. Since information are put away everywhere throughout the systems the information is available broadly everywhere throughout the systems such as system servers, on other organization systems, extranets and the corporate intranets. The appropriated database permits just the customer to execute the dates' and to handle particular data's. 

Two sorts of procedures are there to set up distributed database that are close to date and constant, they are: 1. Replication and 2. Duplication

Replication: 

In the distributive database the reasonable programming ventures gets copied and hunt down any modification in the database. This system keeps the entire database same and it is a compelling strategy in which it ingests extra time in light of the range of the database in the appropriated structure. It depends on the amount of databases arranged in the structure. From now on to do this action we must need package of time and resources.

Duplication:

In the distributive framework this instrument recognizes a database and equivalents that database. It sets time for duplication of information's and to acclimate that the dispersed territory has the first information or not. The client in database just adjusts the expert database and thus it will acclimate about the nearby information which is not adjusted. These two systems provide the information consistently in each conveyed area.