Entity Relationship Diagram
An Entity Relationship Diagram is a model diagram that is used in the system in order to which is also called as ER diagram. The relations between the various entities of the database could be developed in this ER diagram. These diagrams are the logical structure of the databases that are used to deliver the requirements of the database design which is going to be developed. The following is the ER diagram for the given case study.
Figure 1. ER diagram.
Relational Model
The purpose of the relational is that to model the data with the relations in the form of a table. The conceptual model is created in the Entity Relationship diagram and then diagram is then converted into the relational model (Radoslava Kraleva, 2018). The relational model will be highly useful for creating the databases with the help of the database languages like SQL. The following relational model here will be showing the data storage in the relational database of the website which is going to be developed. The relations between the data and the attributes could be easily understood here with the help of his relational model.
Figure 2. Relational Model.
Sample Screen of the Online Order
A sample screen should be designed and created in order to clearly understand the various requirements and how the user interact with the developed system. The screen has been developed with the tool named Balsamiq, which is used to create mockups. The design screen will be showing the requirements that are expected by the owner of the organization in order to make the entire system computerized. The following screen shows the customer details with additional phone numbers, the orders that are placed by the customers and the status of the orders by the customers. This is helpful in order to create and design the website front along the database design in the back.
Figure 3. Sample Screen.
Does your database design allow the storage of all the required information?
A database design that is design should be fulfilling and comprising of all the data that are asked in the requirements of the customer. The developed database design for the given case study is highly based on the customer requirements. Each and every customer requirements are designed in the aspect of development of the website both the front end and backend. The database storage system will be holding all the data that are generated from the customer requirements. This could be well understood with the help of the Entity Relationship Diagram (Ravi, 2020). Here, the entities will be the tables of the database where the attributes will be the data that is to be stored in the tables. The attributes that are in each entity will be based on the proper storage of the requirement. For example, the details of the order will be stored in the order table where the order ID, kit name, scale and the count will be stored. Likewise each and every requirements are clearly analyzed and then the website database has been developed considering to avoid the future issues from the database and its design (Il-Yeol Song, 1995). Thus, it could be said that all the required information will be able to be stored in the database that can be developed with the help of this model diagrams.
What changes, if any, did you make to your initial ER diagram and relational model after you created the sample input screen?
There are minor changes that have been made on the ER diagram as well as the relational model after creating the sample screen for the online order of the CS Hobbies. The sample screen will be used to view the various details of the orders that have been made (Mohammed Abdallh Otair, 2015). The sample screen has been developed with the help of ER diagram and its attributes. There occurs a contraction between the ER diagram and sample screen of the website. The changes are made in the entities that are created initially, status entity has been added after the creation of the sample screen. This was initially planned with the order itself and then it has been created as a new entity in ER diagram and the changes has been made in relational model.
References
Il-Yeol Song, M. E. (1995). A Comparative Analysis of Entity-Relationship Diagrams. Journal of Computer and Software Engineering, 427-459.
Mohammed Abdallh Otair, A. O. (2015). Enhancing an end user development in database design using entity relationship diagram Mapper. Journal of Theoretical and Applied Information Technology , 218-228.
Radoslava Kraleva, V. K. (2018). Design and Analysis of a Relational Database for Behavioral Experiments Data Processing. International Journal of Online Engineering, 117-132.
Ravi, S. Y. (2020). A Study on Comparison of UML and ER Diagram. International Research Journal of Engineering and Technology, 7575-7580.
No comments:
Post a Comment