ScenarioYou have been asked to develop a pizza ordering application. Here is the information your manager just shared with you about this software development project. The pizza ordering application allows customers with a web browser to order pizza for home delivery. To place an order, a customer would search to find items to purchase (specialty pizzas, sodas, desserts, salads, etc.), and then add items one at a time to a shopping cart. They could also view a page that showed the daily special. The customer could search again for more items if they wanted. They would also have the option to build their own pizza with as many toppings as they liked. When all items were chosen, the customer would see the cost of their order, and also be prompted to provide a delivery address for that specific order. If not paying with cash, the customer would provide credit or debit card information for use on the current order. The system should have an option for customers to register with the pizza shop. They could then save their name, address information and e-mail address, so that they wouldn’t have to enter this information every time they placed an order. If they didn’t want to save their personal details on the site, they could register their e-mail address only, which would let them receive coupons and updates on special promotions. To complete this assignment, make assumptions as needed--just be sure to document any assumptions you make. Milestone #1 1.  Identify the following information about the pizza ordering application: a.  Purpose or goal of the system b.  Primary user(s) of the system 2.  Assume the role of the customer. Identify 10 user requirements in user story format “As a (role), I want (feature), so that I can (justification/benefit).” 3.  Identify 5 functional requirements and 2 or more non-functional requirements using the “shall” format from Chapter 4. 4.  Identify 5 use case scenarios and create a simple use case UML diagram for each. Deadline: 3 days. Milestone #2 Complete a UML activity diagram that provides a high level overview of the major processes that characterize the pizza ordering application. 1.  Assume a Test Driven Development approach. Identify 5 or more failing tests and what you would do to make them pass. These tests will form the basis of your unit testing strategy. 2.  Identify whether a plan-driven “waterfall” software development approach or an agile framework or methodology might be more suitable for this software development project. Explain your recommendation. Deadline: 6 days. Milestone #3 1.  Identify the evolution and maintenance related items that should be considered when planning to develop the pizza ordering software application. 2.  Identify ten or more risks that could develop with this project. What is the probability or likelihood that each risk might occur, and what would be the effect to your pizza ordering application if it did? What is your plan to either avoid, minimize or recover from (i.e., contingency plan) each of these risks if they were to occur?  Present your risk analysis as a Risk Register in a tabular format, with the highest impacts/effects listed first. a.  Project Planning Assignments: b.  Plan-driven “waterfall” planning approach assignment: Use the 10 user story requirements from Milestone #1 for this assignment. For each user story, identify the effort in person-days and duration of each deliverable. If one user story is dependent on another, identify that relationship. i.  Agile SCRUM planning approach assignment: Use the 10 user story requirements from Milestone #1 for this assignment. Assuming a 2-week sprint cycle or iteration, identify how many sprints this software development project will take to complete. Identify which user stories will be completed within each sprint and what considerations went into your sizing decision. ii.  Be sure to rank the user stories from highest to lowest priority. 3.  Be sure the most important user stories are completed before the least important user stories. Deadline: 9 Days.

Assignment Instructions:ACME, Inc. is growing like crazy! Now, we need to put into place a more secure and faster connection between our headquarters and our satellite offices. The two locations are approximately one mile apart and are in a heavily populated area.You can make assumptions as to what technologies, cabling, etc. are available.In a Word document, you need to lay out, how you would connect these two facilities together using what you feel to be the best solution.Include a budget, figures are going to be a range, which is understoodWhat technologies, hardware, software, cabling, etc. are you using to make the connectionWhy is your choice the best choice (justify!)?

I attached all the requirements about this.Detail explanation about explanation is on either pdf or comments.Ask me anything if there is something confusing.Step 1:Fill in WordSet.cpp○ Your implementation must be done via a hash table, as described in lecture.○ Your collision resolution policy must be quadratic probing.○ You must use a dynamically-allocated array, not a std::vector or similar container, as the basis in your WordSet.○ Your implementation must fit the interface given○ Your implementation does not need to be templated -- nor should it be, for the purposes of this assignment. ■ In fact, doing so will cause an issue for some of our provided tests.○ You do need to implement the destructor.○ Do not hard code your table for the uses we’ll have in the next section.○ You must also fill in the desired hash function: treating words as numeric types. ■ Be careful about when you take the modulus within the hash function. ■ Be careful about when you take the modulus outside the hash function.Step 2:Write function std::string convert(std::string s1, std::string s2, const WordSet & words) in proj3.cpp○ This function will return the conversion between s1 and s2, according to the lowest Lewis Carroll distance. Separate consecutive words with [space]-->[space]. If there are two or more equally least Lewis Carroll distance ways to convert between the two words, you may return any of them.○ It is recommended that you compute the distance via a breadth-first search. To visualize this, imagine a graph where the words are vertices and two vertices share an (undirected) edge if they are one letter apart.○ A good thing to do the first time you see a word in the previous part is to place it into a map, where the key is the word you just saw and the value is the word that you saw immediately before it. This will allow you to later produce the path: you know the last word, and you know the prior word for each word in the path except the first. Furthermore, if the key isn’t in that map, this tells you that you haven’t seen it before.○ Your implementation does not have to be the most efficient thing ever, but it cannot be “too slow.” In general, any test case that takes over a minute on the grader’s computer may be deemed a wrong answer, even if it will later return a correct one.