Those who are free of resentful thoughts surely find peace. - Buddha
Posted on 20th Jan 2017
The process of doing database design generally consists of a number of steps which will be carried out by the database designer. Usually, the designer must:
Requirements specification -> Requirement Analysis -> Conceptual design (Entity-Relationship Model )-> Logical Schema Design/Implementation Design(Database Schema)-> Physical Schema Design(Access Paths)-> Optimisation
For example: The business is a Dainty Meal(DaMe) company. The business provides it's services by providing their customers:
In order to facilitate these services above, DaMe company had tie up with many restaurants in different cities. DaMe surveys the restaurant and collect information (text and picture)like-
Once all the requirements have been collected and analyzed, the next step is to create a conceptual shema for the database, using a high level conceptual data model. This phase is called conceptual design.
The result of this phase is an Entity-Relationship (ER) diagram or UML class diagram. It is a high-level data model of the specific application area. It describes how different entities (objects, items) are related to each other. It also describes what attributes (features) each entity has. It includes the definitions of all the concepts (entities, attributes) of the application area.
During or after the conceptual shema design, the basic data model operations can be used to specify the high-level user operations identified during the functional analysis. This also serves to confirm that the conceptual schema meets all the indenfied functional requirements. There are several notations to draw the ER diagram.
The requirements document can then be analysed and turned into a basic data set (as shown below) which can be converted into a conceptual model. The end result of the conceptual design phase is a conceptual data model (Figure 1), which provides little information of how the database system will eventually be implemented. The conceptual data model is simply a high-level overview of the database system.
Let's next see how we make a conceptual design from the above analyzied requirements:(We had tried to break the en)
(This post is still in progress as the author is busy in some other stuffs :P. Regret for inconvience. Would finish it sooner as possible)
Good, better, best. Never let it rest. Untill your good is better and your better is best. - St. Jerome