RELATIONAL DATABASE PROPOSAL PROJECT ONE TO MANY RELATIONSHIP

 REQUIRES MS OFFICE ACCESS DATABASE CONCEPTS -Keep the topic “simple”, only 2 entities are needed to apply the concepts covered in the course. The topic must be based on a one-to-many relationship -Follow the outline below (you must include the outline as section labels in your submission, the proposal must be 700+ words in length). 1) Project Name. (5%) Name of the project 2) Purpose. (10%) Explain the purpose of the database. 3) Entities. (20%) 3.1 Describe the entities that will be the focus of the project (You only need 2 entities – be careful – limit your topic – contact the instructor if you are having difficulty). 3.2 Discuss the type of information to be stored in each entity, and what a row in each entity represents. You are strongly urged to limit this to 2 entities. IF you include more than 2 entities – explain why. 3.3 Define each entity using the phrase “EntityName is a …..” and complete the defitnion. For example a”A Student is a person who is enrolled in the university.” 3.3 For each entity you need to list the attributes and the primary key. Also designate the foreign key field(s). Use the following format: Department(DeptID, DeptName, Location) The primary key is DeptID. Employee(EmpID, FirstName, LastName, Street, City, Zip, Phone, DeptID) The primary key id EmpID. DeptID serves as a foreign key. 4) Questions. (10%) What question would you like the database to be able to process – the question should require content from both proposed entities. 5) Users and Administrators. (10%) Users and administrators – explain who will use and who administer the database. 6) Recording and Used Without Database. (10%) Explain how this information would be recorded and used without a database 7) Relationship. (15%) 7.1 Explain the relationship between the entities. 7.2 You must have a one-to-man relationship between the proposed entities – explain how you expect each row in one entity (table) will relate to a row or rows in the other table (entity). 7.4 Include statements reflecting the relationships and multiplicity constraints in both directions. For example, consider the following: Each Department may have many Employee(s) assigned. Each Employee may be assigned to a Department. Note that the above example accommodates the business rules: 1) An employee may not be assigned to a Department (the president for example). 2) A Department may not have any Employee assigned to it as well (like when it is first set up). These business rules may not apply to all organizations. REJECTED TOPICS:projects that track statistics, keeping track of movies or DVDs, Recipes, Students and Classes, modifications to examples in our text, or examples in other textbooks (Premier Products, Henry Books, Marina Group, Orders and Parts, Customer and Orders, or Customers and Products), Cars and Owners, Owners and Rental locations, Products or Parts / Suppliers, IT asset tracking, Books and Authors, Physical fitness tracking, Flight and Tail-numbers, and Game based topics.