Beranda / Database Design / Desain Basis data

Database Design

Database Design

The necessities and the collection analysis phase produce both facts requirements and purposeful requirements. The facts requirements are used as a source of database layout. The information requirements ought to be laid out in as distinctive and whole shape as viable.

Conceptual layout

  • as soon as all of the necessities were accrued and analyzed, the subsequent step is to create a conceptual schema for the database, using a high level conceptual records model. This segment is called conceptual design.
  • The result of this segment is an Entity-courting (ER) diagram or UML class diagram. It's miles a high-level information model of the precise application vicinity. It describes how distinct entities (gadgets, gadgets) are related to every other. It also describes what attributes (features) every entity has. It consists of the definitions of all of the principles (entities, attributes) of the utility area.
  • At some point of or after the conceptual schema layout, the basic facts model operations may be used to specify the high-degree user operations recognized at some stage in the useful analysis. This also serves to confirm that the conceptual schema meets all the identified useful necessities.


There are several notations to draw the ER diagram.

Logical design

  • The result of the logical layout section (or information version mapping phase) is a hard and fast of relation schema. The ER diagram or magnificence diagram is the idea for those relation schema.
  • To create the relation schema is quite a mechanical operation. There are regulations how the ER model or class diagram is transferred to relation schema.
  • The relation schema are the idea for desk definitions. In this segment (if now not executed in previous section) the primary keys and overseas keys are described.

Normalization

  • Normalization is the remaining a part of the logical layout. The aim of normalization is to dispose of redundancy and capability update anomalies.
  • Redundancy way that the identical statistics is stored more than once in a database. Replace anomaly is a effect of redundancy. If a bit of information is stored in more than one vicinity, the equal data have to be updated in multiple location.
  • Normalization is a technique via which you'll be able to alter the relation schema to lessen the redundancy. Every normalization section adds greater members of the family (tables) into the database.

Bodily layout

  • The intention of the ultimate section of database layout, bodily layout, is to implement the database. At this segment one ought to realize which database control gadget (DBMS) is used. As an example, different DBMS's have distinct names for datatypes and have exclusive datatypes.
  • The square clauses to create the database are written. The indexes, the integrity constraints (regulations) and the customers' access rights are described.
  • Sooner or later the information to test the database is introduced in.

In parallel with these sports, application packages are designed. The implementation of the packages can start while the database is created and records has been introduced in. Supply: Elmasri, Navathe. 2004. Fundamentals of Database systems. Addison-Wesley. Chapter 3. Records Modelling using the Entity-relationship version.