Implementing a database, company GLOVO, digital-literate, databases, language, fast communication between the different system, accessing suitable information quickly, recording of all transactions, Entity Relationship Diagram
You are required to write a summative report for the company's senior management and shareholders, who you are to assume are not digital-literate in relation to databases, therefore the language should be clear and any technical terms used should be explained. The report should introduce the company, clearly explain what a database is, what typical functions the proposed database will perform (by clearly listing and describing the kinds of transactions the database is likely to carry out which will help with the day-to-day functions of the organisation, that is to say, what will the database actually do).
[...] And in an entity set we add all the elements that are related to the database. We have different types of Entity relationship diagram as: • Crow Feet Notation Diagram • UML notation diagram Fig.2: Entity Relationship Diagram Create a Data dictionary for the entity relationship model using the entities and attributes identified in part b). The data dictionary should clearly list the attributes, identifying primary and foreign keys, data types and any constraints/business that have been identified from your chosen organisation. [...]
[...] • Abié, M. and Afrik, F Côte d'Ivoire : Glovo connecte du marché abidjanais. [online] Financial Afrik. Available from:
[...] The way of operating GLOVO is very simple. A customer who wants to make an order goes to the application and chooses the store where he wants to order from. After the customer chooses the specific product that he wants from that store, it's possible to choose different product but in only one store, he continues to order confirmation where he has to confirm the quantity and accept the estimated cost. After the customer has chosen his specific payment type and validated the billing, the order will be sent to the shipping system where a deliverer will be requested for delivery. [...]
[...] ER modelling help to analyse data and produce a well-designed system. This model is the best in terms of showing real-world entities and make the relationship between them (Bogatee, 2021). In all, I can argue that the database supports all the transactions clearly due to the way that the organization is clean and visible. We can easily manipulate information because all the tables and data are well organized so the different SQL statement is also good and executable. References • C Comment commander sur Glovo [online] comment.ma. [...]
[...] How the use of ER modelling is important in the design of a database solution. Any assumptions that you have made. How the database supports the transactions that you identified in Task 1. Answer in my opinion, the database created has met the requirement. Because the GLOVO database system permit to receive the order quickly and make the transaction between the order and the customer, it permits to link each relationship between the tables (primary key and foreign key). All data are normalized and didn't have redundant information. [...]
using our reader.