Prior to beginning work on this assignment, read Chapter 1, sections 1.3, 1.6, 1.8, 1.11, 1.14, 1.17, and 1.20 in Data Structures Essentials; Chapter 9 in Data Structures and Algorithm Analysis (Links to an external site.); the Trail: Collections > Algorithms from the Java Tutorials (Links to an external site.); and the Binary Search and Application (Links to an external site.) article.Students: Be sure to download and save a PDF version of your textbook for future reference. It will be used in later courses within your program, including the final, capstone course. Zybooks limits online access to your course textbooks to a 12-month period. (Zybook Download Instructions)For this assignment, you were just hired as a junior software developer as part of a team of developers for a software contracting company. Your company has just won a big contract to develop a software application for the United States Department of Defense. The team lead has tasked you with developing a Java program that uses a binary search algorithm looking for the numbers 17 and 45 from an array. Because you do not have your secret clearance yet, a senior developer will later take your code and modify it for the requirements of the contract.In this coding assignment you will utilize the Java syntax and techniques you learned while reviewing the required resources for Week 2. Include comments for each section of the program. You may select appropriate variable names as long as proper Java syntax is used. You will also submit your source code.Input:In the input section, you are to create a Java program that uses a binary search looking for the numbers 17 and 45 from an array. Since you are a junior developer, hard code the array as follows:{5,10,15,20,25,30,35,40,45,50,55,60,65,70}Processing:In the processing section, use the appropriate Java syntax to perform the lookup.Output:Your display must include the following:A prompt indicating if 17 was foundA prompt indicating if 45 was foundYour code must include the following as comments:Name of programAuthor/student’s nameCourse name and numberInstructor’s nameDate submittedTake a screen shot of the results page and save the image. When you are finished with your Java program, zip the file(s). Next, submit the zip folder that contains the running source code to the Week 2 Zip File Submission page. If you need more guidance, review the Zip File Quick Start Guide. Be sure that you are sharing the zip folder with your instructor only. Your instructor will run your source code to ensure that the functionality runs correctly.In a Word document, express the various types of algorithms, including searching and sorting used in your Java program in a minimum of 200 words. Paste the image of your results and your source code into the document. Submit your Word document to Waypoint for grading.

Using ER Assistant (recommended) or Visio, create an ER diagram (ERD) that has at least 5 entities but no more than 6 entities. Each entity must have a minimum of 5 attributes that full describe that entity. The 5 attribute minimum includes the primary key only (see note below about foreign keys in ER diagrams).All entities must be connected with suitable relationship that describe not only the cardinality (1:1, 1:M, M:M) but also whether the relationship is mandatory or optional.Every entity and relationship in your diagram must have comments describing your business rules, i.e. the purpose of the entity and attributes, its relationship cardinality, and if it is mandatory or optional. You may embed these comments into the ERD using ‘Design Notes’/‘Design Justification’ inserts or provide them in a separate Word document.Crow’s Feet notation style is required for all relationships. If you use ER Assistant, this is the default notation style. If you use Visio, you must ensure that you properly set the use of Crow’s Feet notation prior to submitting your final ERD.Your ERD must be free of errors to receive full points. Hint: ER Assistant provides automated checks to ensure the ERD error free using the ‘Check Diagram’ function.Deliverable:Submit the ER diagram you created as an .ERD (ER Assistant) or .VSD (Visio) file. Note: Foreign keys are not explicitly added in ER diagrams because foreign keys are not a construct of entity models but rather relational models. This means that you will not add a foreign key attributes to your entities. Your suitable relationships are all that is needed to determine where the foreign key is designed to go. For example, say you have a CUSTOMER and ORDER entity each with their own primary key (CUST_ID and ORDER_ID) with a 1:M relationship such that one and only one customer places zero, one, or many orders. It follows then that CUST_ID is a foreign key within the ORDER entity without explicitly placing a CUST_ID foreign key as an attribute on the ORDER entity.