Week 3 – Data Management Project: Logical Design

computer science question and need guidance to help me learn.

The Data Management Project for week 3 builds upon what you did for the Data Management Project in weeks 1 and 2. Create a logical data model of data management project showing the entities, relationships, primary keys, and foreign keys. Eliminate composite attributes, like student_name, by creating student_first_name and student_last_name. Create associative entities to resolve any many-to-many relationships between entities. Make sure each entity is in third normal form, meaning that each non-key attribute must depend on the primary key, the whole primary key, and only nothing but the primary key. Use the Diagrams.net (formerly draw.io) tool (https://app.diagrams.net/) to create your logical model.
Requirements:

IST 7000- Data Management
01/15/2021
The database is a part of a bigger system called an information system, which is in charge of storing, retrieving, and gathering data.The database is utilized for data analysis as well. Individuals, hardware, software, and databases make up the information systems. An information system’s database design is its most important component.
In order to help eliminate anomalies and omit some essential information, an efficient database design should always offer a database that does not tolerate duplication. Effective data access is a requirement of every good database. The information system’s requirements should also be supported by and met by the database. Database designers should continually keep the system’s requirements in mind.
The problem a database is supposed to solve
The database I am going to develop is a flower shop management system database which is going to store all the information about the flower shop. The information will include employees, information, inventory, customers, and complete sales order. The information about the employees in the database will include the employees information, salary, and their date of hire. The inventory database will include product ID, product retail price, product vendor price, description, product color and quantity. The customers database will include first and last name, customer ID, and customer address. The information about the complete sales order database will include sales order, date of order, customer first and last name, employee ID, and the status of the order.
After the database is created, the flower shop’s issue of having to use a manual file system, wherein it records the details of its staff, clients, inventory, and completed sales on paper, will be resolved. As long as the employees have a username and password to access the database, it will be online and accessible from anywhere.
The constraints associated with the database project
Constraints are necessary for every database, but they are especially necessary for relational database architectures. A relational database supports a coherent idea of constraints. The restrictions will be essential because I can design unique semantics for the database thanks to them. A given entity will then be subject to the constraints to see if it meets with particular semantic requirements.
The following limitations will be part of my database project. Entity integrity is the first one, which mandates that each entity have a primary key and that each primary key not be null. If null values are allowed in the primary, some rows will be impossible for me to identify. The second constraint, known as referential integrity, requires that every foreign key has a primary key that is identical to it.
The objectives you what to accomplish by designing a database
In order to ensure that the database can be used to support the goals and objectives of the business, database design aims to provide an efficient and effective representation of the data and relationships in a system.
The scope of your database design project
To make sure that the finished database system satisfies the needs of the flower shop, the scope of a database design project should be precisely specified, accepted by all stakeholders, and reviewed and modified frequently throughout the project.
The boundaries that describe what is and what is not included in your database project
The area that the project will cover is defined by its borders. The boundary statement assists in identifying all issues that are specifically pertinent to the desired project and eliminates all other topics. The significance of the project boundary provides a point on the curve that shows how resource consumption rises and performance declines when the border is crossed. However, a larger performance range for the system leads to greater performance, thus working around limitations isn’t always the best course of action. By observing and evaluating the system modules, the product’s ideal work range is offered.
PRODUCTSPKProduct_IdNameDescriptionPriceQuantity in stockComplete Sales OrderPKSales_Order_IdSales_Order_DateCustomer_Id LookupEmployee-Id LookupOrder_Status EMPLOYEEPKEmployee_IdEmployee_NameEmployee_AddressEmployee_phone NumberEmployee_Salary Date_of_HirePurchase Order PKPurchase_Order_IdPurchase_Order_NumberEmployee_ID Look UpVendor_Id_ Look UpStatus CUSTOMERSPKCustomer_IdCustomer_NameCustomer_Address Customer_Phone NumberCustomer_EmailDaisy Flower Shop Database Management VendorPKVendor_IdVendor_NameVendor_Street Address Vendor_CityVendor_StateVendor_zip code TablePKUniqueIDRow 1Row 2Row 3INVENTORYPKProduct_IdProduct_DescriptionProduct_ColorProduct_AmountProduct_Retail_Value