How would you improve the database design diagram you created for the package shipping information system requirements scenario (Unit Scenario) you submitted last week (Unit 08: Database Design)?
Reader Interactions
Comments
Leave a Reply
You must be logged in to post a comment.
I would first list the entities and their attributes followed by assigning their relationships to other entities, and then improve the overall visual appeal of my diagram. For instance, coloring the different types or classes of entities to help the users understanding.
I would eliminate duplicate attributes from different tables.
I would use composite primary keys.
And I would make some cross-reference tables ; however, one thing needs to consider is whether to add foreign keys and what foreign keys need to add when adding cross-reference tables.
I would change the layout the the diagram, and use clear and understandable entity names(for identification) and try my best not to make the relationship lines cross.
I would like to add some information about the situation in the warehouse during the shipping process.
Add and modify the properties of the entities, and represent their relationships in a clearer way
I would like to use more concise language to describe the relationship between entities to make the diagram clearer.
I would like to reduce some attributes that are of little importance.
1: I will use a more exact entity name, such as changing the service order line to service information system.
2: The relationship between employee and warehouse should be: an employee can go to multiple warehouses, and a warehouse can have multiple employees to deliver goods.
3: The primary key and foreign key are not marked in the chart. Although the primary key of each table can be identified, it is not clearly identified. I will bold the primary key attribute in each table.
4: Foreign keys are not shown in the chart. I will use the foreign key logo to identify the foreign key.
5: The icon does not indicate the association between different tables. For example, a customer can have multiple orders, but an order must have one customer. The relationship between the order and the customer needs to be expressed by crowd foot notation.
I think the following points should be changed:
1. Customer can delete the two attributes of “customer Email” and “customer ID”, and add the attribute of payment method.
2. Service Order should be added with “customer number” or it cannot form a relationship with customer.
3. Add “package description” attribute to Service Order Line
4. Improve employee information and implement responsibilities and obligations on each employee. In addition to the attributes in the table, the two attributes “Job position” and “responsible for the street” are added.
5. Change to a form making software.
1. Adjust the relationship between entities to make the graph more intuitive and clear.
2. Modify the attributes of some entities to make the names of the same attributes more uniform.
3. Mark the primary key in the graph to identify it more clearly.
I would reconsider the one-to-many and one-to-one relationships between each entity.
I will improve my database blueprint in two ways.
1. We should have two databases simultaneously, billing and payment. After receiving the request, we will store separately the request report related to the order and the order payment report, and both would be send to Bill.
2. Set a boundary during drawing to distinguish internal information and external information.
After reviewing the database design drawings of the previous job, I noticed that I had some changes that needed to be made.
1. Add some key relationships that are missing in the figure.
2. Remove duplicate attributes from different tables.
3. Consider how to cross-reference.
1. Eliminate duplicate attributes to reduce data redundancy
2. Use a composite primary key
3. Make a cross-reference table and consider whether to add foreign keys and which foreign keys need to be added.
4. Enrich the entity attributes in specific tables from a business perspective
5. Customer should be a one-to-one relationship, there may be errors in the last submission
6. There should be specific customer information in the Individual form, the assignment submitted last time did not cover.
Use more concise language to describe the relationships between the entities to make the diagram clearer.
Eliminate duplicate attributes from different tables.
I will use a more concise language to describe the relationship between entities and remove duplicate attributes to make the diagram clearer
I think the database design diagram I submitted should be improved:
1.Add or subtract entity attributes as appropriate
2.Add a primary key to the chart
3.Move the entity position appropriately and add color to the lines to make the chart clearer, simpler and more beautiful
I think maybe the delivery order entity is missing in this diagram,so I will add it in the diagram.And the delivery order should build the relationship with the warehouse and the employee.Because the warehouse should send the delivery order to the employee and the employee should receive the delivery order from the warehouse and employee should deliver the good to the customer based on the delivery order.Mark the primary key in the graph to identify it more clearly.So I will try my best to complete the system better.
If I was asked to take actions to do change for this system by improving the database design diagram, firstly I will reconsider if the functions for prevent the occurrence of risk can be efficient as expected. Secondly, I will add some explanations in the database design diagram.
First list the entities and their attributes, then assign their relationships to other entities, and then improve the overall visual appeal of my chart. For example, coloring entities of different types or categories to help users understand
I will improve the database of customer receipt notice and goods payment in real time.
1. Add the goods receiving system, so that managers and inventory managers can know whether the delivery of goods really exists, whether the customer signs in, and whether the transaction really occurs.
2. Different customers will adopt different payment methods. Therefore, adding the real-time database of goods payment can help the financial personnel to distinguish between the customers who have paid and those who have paid for goods, so as to facilitate the later collection of money. In addition, some customers will purchase goods on credit, so the data of goods payment needs to be integrated
1. Add some key relationships for drawing totals.
2. Consider how to cross-reference
3. Delete duplicate attributes to reduce data redundancy
4. Use composite primary keys
5. Make a cross-reference table, and consider whether to add foreign keys and which foreign keys need to be added.
According to the requirements of the information system, I plan to add additional entities I lost and related attributes, as well as the relationship between different entities.
I’ll also label the primary key in each entity
I will modify the properties of the entities and make the relationships between the entities clearer
I will add more entities ,such as the person customer,business customer and package and so on ..And I maybe change some relationship between entities.The diagram I post before may have some mistakes in the setting of prime key and foreign key.
I think I will adjust the relationship between each entity. And set a boundary between the internal system and the external system to distinguish it. And be sure to let the boundary be displayed in the information system.
The first is to clarify the relationship between the entities. The abstraction of the ER diagram must not be separated from the prototype, but must match the requirements analysis and the actual situation.
The second is to make clear that there is a sequence between entities and that business processes cannot be reversed.