Below is the original assignment directions:

Below is my database table (entities, attributes, etc.) for the specific company I chose. Event Scheduling.

Below are the things that should he completed:

Overall the assignment is to choose/create a company, then create a database for it. Then conduct an executive summary and list of business rules. all information is listed above, including the template of how the completed assignment should be laid out.

The last page is in a foreign language for the sake of knowing how the setup should be. The tenplate is simply showing the viewer how the business rules (when created) should be listed.

CIS 2980 Database Project Design Documentation Use the project documentation template to write your main design document and guide you through the various components of the project. Remember, the better you document each component, the easier it will be for the instructor to locate. You want to make your instructor's (boss's) job easier. This document is the key to my grading your project. Failure to properly document your database and design will increase the time required to grade your project and will result in a lower score. Your instructor reserves the right to lower scores if s/he has to search your project to link design, implementation, and requirements together. Note the organization, formatting, and other details of the template. You should maintain these throughout the document to keep a professional appearance. Notes about page one: Provide a title for your project based on the topic. This is in small caps, 16 point 1 The subtitle is optional Use your first and last name. Put the date in formation of "month day, year", e.g. January 1, 2019 Executive Summary Write an executive summary that explains the application, the entities, relationships, and any other relevant information. This is an important summary that will help you guide and organize your thoughts, make decisions, and help define your project to the reader. In some ways, this is similar to a proposal, but it's already been proposed and accepted, so you are summarizing the purpose of the project, the high level overview of it, and what is accomplished. Assume the reader is intelligent, but has little or no knowledge of databases and is not familiar with your application or any particular technical knowledge. Avoid using technical database terms and jargon such as relations, foreign keys, indexes, etc. Use good grammar and spelling. Do not extend it past the first page. You should have an introduction describing the purpose, including some background information to understand the foundation of your chosen topic. The body should summarize and explain the application, entities, relationships, etc., without technical jargon but having enough details that the reader understands. The conclusion should summarize. Do not use the phrase, "In conclus, ...". You are basically summarizing what the project is accomplishing. Revise as necessary while designing and implementing your project. The design document template has some notes and comments to help guide you create it. I. Business Rules Write out the business rules that provide the foundation of your application. Each relationship is bidirectional. therefore you should have two business rules for every relationship in your databases. Make sure the business rules clearly define the optionality/connectivity of the relationships. Include additional business rules if they define specific constraints. This section should be of necessary length to clearly define all your business rules. Name: Haeven Durbin Topic: Event Scheduling Title: Compassion International LLC Description: Event scheduling involves the scheduling of events according to the needs of a customer. Event scheduling is one of the most important sectors. Additionally, designing a database for such a system can be deemed challenging. While we design the database, for any topic, we divide the complete database components. The different components for the event scheduling system consist of Login, Registration, Supplier Payments, Orders, Billing, and Feedback. Entities-List your entities (i.e. tables) that will meet project requirements. Entity 1: Registration Entity 2: Entity 3: Entity 4: Entity 5: Entity 6: Login Suppliers Payments Orders Billings Feedback User ID, Password, First name, Last name, Address, DOB, City, State, Mobile Number, Contact Number, Email ID Email Address, Password Date, Supplier Name, Supplier Company, Amount Order Number, Email Address, Event Code, Approximate Number, Category Bill Number, Order Number, Email Address, Amount, Tax, Delivery Charge, Final Amount, Bill Date Email ID. Subiect. Message. Ratings INTERNATIONAL COMPARISON LLC. Event Scheduling Haeven Durbin Respectfully Submitted To: Curtis Penrod I June 24, 2022 Executive Summary I. Business Rules Nunc consectetur tortor eget feugiat aliquam. Proin venenatis facilisis est, quis dictum elit ullamcorper vel. Nam mollis ut justo at pharetra. Quisque a porttitor sapien. Donec convallis risus ac ex pulvinar iaculis. In hac habitasse platea dictumst. Donec sagittis neque sit amet faucibus pharetra. Etc., etc., etc