create a table of x and y values that represents a linear non proportional relationship and there are more questions

vice. The company has four stores located at malls and is planning on expanding to other locations. Each store has a manager, a technician, and between one and four sales reps. The owners want to create a personnel records database, and they asked you to review a table that they had designed. They suggested fields for Store Number, location, store telephone, manager name, and manager home telephone. They also want fields for technician name and technician home telephone and fields for up to four sales rep names and sales rep home telephones. Draw an Entity Relationship Diagram modeling their suggested design. Analyze their original design using the normalization concepts you learned in Module 9. For this part of the question, make sure you begin with the original table in an unnormalized form as requested by the company. Work your way through 1st, 2nd, and 3rd normal forms. At each point, be sure you use the standard notation format to show the changes in the structure of your table(s) (Module 9; 9.6.1). During your analysis, be sure to explicitly illustrate/write about the reason behind the design decisions you make. Additionally, each normal form should have it's own section/heading. Draw a final ERD showing your final analysis showing the relationship among the entities you identified during normalization

rvice. The company has four stores located at malls and is planning on expanding to other locations. Each store has a manager, a technician, and between one and four sales reps. The owners want to create a personnel records database, and they asked you to review a table that they had designed. They suggested fields for Store Number, location, store telephone, manager name, and manager home telephone. They also want fields for technician name and technician home telephone and fields for up to four sales rep names and sales rep home telephones. a. Draw an Entity Relationship Diagram modeling their suggested design. b. Analyze their original design using the normalization concepts you learned in Module 9. For this part of the question, make sure you begin with the original table in an unnormalized form as requested by the company. Work your way through 1st, 2nd, and 3rd normal forms. At each point, be sure you use the standard notation format to show the changes in the structure of your table(s) (Module 9; 9.6.1). During your analysis, be sure to explicitly illustrate/write about the reason behind the design decisions you make. Additionally, each normal form should have it's own section/heading. c. Draw a final ERD showing your final analysis showing the relationship among the entities you identified during normalization

nbow is the shape of a parabola. The equation for this parabola is y = -x2 + 36. Graph of a parabola opening down at the vertex 0 comma 36 crossing the x–axis at negative 6 comma 0 and 6 comma 0. Create a table of values for a linear function. A drone is in the distance, flying upward in a straight line. It intersects the rainbow at two points. Choose the points where your drone intersects the parabola and create a table of at least four values for the function. Remember to include the two points of intersection in your table. Analyze the two functions. Answer the following reflection questions in complete sentences. What is the domain and range of the rainbow? Explain what the domain and range represent. Do all of the values make sense in this situation? Why or why not? What are the x- and y-intercepts of the rainbow? Explain what each intercept represents. Is the linear function you created positive or negative? Explain. What are the solutions or solution to the system of equations created? Explain what it or they represent.

You will use a single backing array(instead of two) and two hash functions (both MultiplicativeHashFunction objects), h1 and h2. The z values for your hash functions (and all subsequent hash functions needed when resizing or rehashing) will be taken from an array of integers passed to the CuckooHashTable constructor. The first value in the array will be used for the first incarnation of h1, the second value for the first incarnation of h2, the next two values will be used for the next incarnations of h1 and h2, etc. Note: be careful to follow this. We will be checking your array (via toString()) and correctness will depend on using the same values of z as we do when generating the test code. The MultiplicativeHashFunction objects you will use also have a getParams() method to show the value of z,w,d when that hash function is used. When adding an item, x, that is not in the hash table already, always add it to t[h1(x)] (even if t[h1(x)] is already taken and t[h2(x)] is available). The load factor must always satisfy α=n/t.length≤1/2. If adding an item will violate this then resize the table (doubling its size) and rehash everything (before doing the add). After removing an item, if the load factor satisfies α=n/t.length<1/8 AND the dimension satisfies d≥5 then resize by reducing the size of the bucket table by a factor 2 and rehash everything. Each time you resize you will create two new hash functions using the next two z values (that were initially passed to the constructor). Your constructor should initialize an empty bucket array of size 16 (i.e., d=4). This is the minimum size your bucket array should ever be. Never let the dimension be smaller then 4.