Have an assignment in two parts, example and assignment description attached. need it completed in to separate parts according to directions
USING MYSQL TOPIC SELECTED: B. Student Database Management 1. A college contains many departments, and each department can offer any number of courses. 2. Many instructors work in the department, but instructors can work only in one department. 3. Each instructor can take any number of courses and a course can be taken by only one instructor. 4. Students can enroll in any number of courses. However, there is a limit on how many credits a student can take INSTRUCTIONS FOR PROPOSAL: From the project selected(LESSON 2), submit a 2-3 page paper with the project proposal. The proposal must consist of a separate cover page indicating the title of your project, the full name and the course number.Description of the problem and various business rules identified at the early stages.Initial list of entities (tables) and the attributes that have been identified. INSTRUCTIONS FOR FINAL PROJECT: Prepare a page, double-spaced book review as a Microsoft Word document using APA current Edition guidelines. The course project must include a title page, an introduction, the body, summary and conclusion paragraph(s), and a reference page. The template provided for the course project will assist you in ensuring that you are meeting APA paper guidelines. The goal in this course project is to synthesize all your resources learned and demonstrate your knowledge by addressing, discussing, comparing, contrasting, interpreting, and distinguishing the subject matter in your review. 1. The course project paper must include a title page, an introduction, business rules, the ER diagrams and the SQL schema, stored procedures, views and triggers and how to run the program and sample screenshots. 2. A separate cover page indicating the title of your project, the full name (with e-mail), the course number. 3. Entity Relationship Model diagram using ER notation. Include all the ER diagrams. 4. The collection of normalized relations and functional dependencies, and a brief discussion as to the normal form(s) achieved, the methods used to achieve these normal forms. 5. The SQL DDL used to create the tables and add primary key and foreign key constraints. (CREATE and INSERT statements). 6. All the stored procedures and functions and triggers created in the project. 7. Conclusion of what you learned and what can be improved in the project. (Sample is attached) Week4_ProjectProposal_Sample.pdf 1 Bike Rental System Project Proposal Prasanth K International American university MIS 560 Database Management Systems Dr. Prasanth Kalakota 2 Introduction Write at least ½ page introduction about project. Business Rules Some of the business rules are 1. User can rent only one bike from any one location. 2. Electricity bill must be separate from rent. 3. Minimum amount has to be deposited before renting. 4. Users can rent for daily or weekly. Entities and Attributes Various Entities observed are LOCATION, CUSTOMER, BIKE TYPE, and RENT. Explain about Primary Keys and Foreign Keys in Entities LOCATION Entity contains the following Attributes • LOC_ID • LOC_NAME • LOC_ADDRESS • LOC_CITY • LOC_STATE • LOC_ZIPCODE CUSTOMER Entity contains the following Attributes • CUST_ID • CUST_FNAME • CUST_LNAME 3 • CUST_ADDRESS • CUST_PHONE BIKE_TYPE Entity contains the following Attributes • BT_ID • BT_NAME RENT Entity contains the following Attributes • RENT_ID • RENT_LOC_ID • RENT_CUST_ID • RENT_BT_ID • RENT_CHECK_OUT_DATE • RENT_CHECK_IN_DATE Relational Diagram Figure 1 shows the Relational diagram between different entities. DBSchema software [Reference Number] is used to create the Relational Diagram. Explain about diagram 4 Figure 1: Relationship diagram 5 References Lastname, C. (2008). Title of the source without caps except Proper Nouns or: First word after colon. The Journal or Publication Italicized and Capped, Vol#(Issue#), Page numbers. Lastname, O. (2010). Online journal using DOI (digital object identifier). Main Online Journal Name, Vol#(Issue#), 159-192. https://doi.org/10.1000/182 DBSchema Software. (n.d.). Retrieved from https://dbschema.com/. https://doi.org/10.1000/182